القائمة
Implement a spec or a single ticket, driving TDD at the seams agreed in the spec.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Scan the session for compound-worthy learnings, then commit the working tree with a repo-appropriate, value-communicating message.
Garbage-collect the knowledge stores — audit docs/solutions/ and AGENTS.md against the current code.
Capture this session's durable learnings and route each to the right knowledge store, every write user-gated. Use at loop end when /commit's opening scan finds candidates, when /diagnosing-bugs closes out a fix, or when the user wants to capture, remember, or write down a learning, convention, gotcha, or preference.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to be grilled about a plan, wants a decision stress-tested, or when requirements are fuzzy before a spec is written.
استنادا إلى تصنيف SOC المهني
| name | implement |
| description | Implement a spec or a single ticket, driving TDD at the seams agreed in the spec. |
| argument-hint | [spec or ticket path; blank asks] |
| disable-model-invocation | true |
| version | 1.0.0 |
| source | mattpocock/skills@1.1.0 (implement) |
Implement the work in the spec (docs/specs/<feature>.md) or the ticket the user names.
Read it in full first; for a ticket, read its parent spec too.
Where the spec agreed a test seam, drive /tdd at that seam — the seams are already approved, so test at them without re-asking.
Where no seam was agreed, implement directly: state explicit verification criteria up front (what observable result proves it works), then verify against them before calling the work done.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
When working from a ticket, tick its acceptance criteria as each one is verified.
Done when every criterion is verified and the full suite passes → close with a flow pointer (presentation) naming the review tail, all in this session with the working diff as context: /simplify (user-invoked) for an optional quality pass, then /review-gate (user-invoked) — suggest low for a trivial or mechanical diff, high for a large, cross-cutting, or risky one, medium otherwise — then /commit (user-invoked).
If context runs low anywhere in that chain, recommend /handoff (user-invoked) and resume in a fresh session instead of pushing on degraded.
