Skill
clarify
Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates…
Data
Skill
/implement
TDD implementation (RED→GREEN→REFACTOR) → verify → review
Install
$ npx -y skills add mag123c/toktrack --skill implement --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/implement
Context preview
The summary Claude sees to decide when to auto-load this skill.
TDD implementation (RED→GREEN→REFACTOR) → verify → review
SKILL.md
implement.SKILL.mdname: implement
description: TDD implementation (RED→GREEN→REFACTOR) → verify → review
required_context:
- .claude/ai-context/architecture.md
- .claude/ai-context/conventions.md
Implement
Flow
Analysis → Gate pre-run → TDD(RED→GREEN→REFACTOR) → /verify → /review → /wrap
Execution
1. **Analysis**: Review plan, identify affected modules
2. **Gate pre-run (MUST — before coding)** Run the PLAN's `[unverified-gate: probe=…]` / Phase 0 probes before RED. Fail → halt + report (don't build on a falsified assumption). Map Acceptance/DoD → RED tests; mark unverifiable as `[unverified-gate]` to carry to verify/wrap. Detail → `references/gates.md` (tag vocab: `../clarify/references/provenance.md`).
Rust-specific probes:
- `cargo check` — whether it compiles
- `cargo test -- --list` — verify test targets exist
- `make check` — unified fmt + clippy + test gate
3. **TDD Cycle**:
- RED: Write failing test first
- GREEN: Minimal code to pass
- REFACTOR: Clean up (keep tests passing)
4. **Auto-call `/verify`**: On implementation complete 5. **Auto-call `/review`**: On verify pass 6. **Auto-call `/wrap`**: On review PASS
Commands
cargo test
cargo clippy -- -D warnings
cargo fmt --check
Rules
- No implementation without test
- On verify fail → fix and retry
- On review FAIL → fix and retry
- Complete full chain without stopping
Read more
name: implement description: TDD implementation (RED→GREEN→REFACTOR) → verify → review required_context: - .claude/ai-context/architecture.md - .claude/ai-context/conventions.md
Implement
Flow
Analysis → Gate pre-run → TDD(RED→GREEN→REFACTOR) → /verify → /review → /wrap
Execution
1. **Analysis**: Review plan, identify affected modules
2. **Gate pre-run (MUST — before coding)** Run the PLAN's `[unverified-gate: probe=…]` / Phase 0 probes before RED. Fail → halt + report (don't build on a falsified assumption). Map Acceptance/DoD → RED tests; mark unverifiable as `[unverified-gate]` to carry to verify/wrap. Detail → `references/gates.md` (tag vocab: `../clarify/references/provenance.md`).
Rust-specific probes:
- `cargo check` — whether it compiles
- `cargo test -- --list` — verify test targets exist
- `make check` — unified fmt + clippy + test gate
3. **TDD Cycle**:
- RED: Write failing test first
- GREEN: Minimal code to pass
- REFACTOR: Clean up (keep tests passing)
4. **Auto-call `/verify`**: On implementation complete 5. **Auto-call `/review`**: On verify pass 6. **Auto-call `/wrap`**: On review PASS
Commands
cargo test cargo clippy -- -D warnings cargo fmt --check
Rules
- No implementation without test
- On verify fail → fix and retry
- On review FAIL → fix and retry
- Complete full chain without stopping
Ships withtoktrack
Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code)
Get the whole plugin