jidoka-implement
/jidoka-implement
Implement the result of /jidoka-to-spec and /jidoka-to-tickets in code, using jidoka-tdd when project instructions allow test-first work. Use for the Build stage of jidoka-full, or when test-first implementation of a spec and tickets is requested.
- Author
- TDSchreur ↗
- Repository
- jidoka ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement the result of /jidoka-to-spec and /jidoka-to-tickets in code, using jidoka-tdd when project instructions allow test-first work. Use for the Build stage of jidoka-full, or when test-first implementation of a spec and tickets is requested.
Original author description
Implement the result of /jidoka-to-spec and /jidoka-to-tickets in code, using jidoka-tdd when project instructions allow test-first work. Use for the Build stage of jidoka-full, or when test-first implementation of a spec and tickets is requested.
How it works
SKILL.md has no level-two headings · 18 lines, 309 words
SKILL.md preview
--- name: jidoka-implement description: "Implement the result of /jidoka-to-spec and /jidoka-to-tickets in code, using jidoka-tdd when project instructions allow test-first work. Use for the Build stage of jidoka-full, or when test-first implementation of a spec and tickets is requested." disable-model-invocation: true --- # Implement Spec Adapted from the `jidoka-implement` skill in mattpocock/skills (MIT); see the license installed with this skill. Implement the provided spec and its tickets on a single feature branch, using test-first development when project instructions allow it. The tickets are a **task graph** with blocking relationships, not a list of steps, so always take a ticket whose blockers are done. The issue tracker should have been provided to you. If not, tell the user to run `/jidoka-setup`. 1. Read the spec and tickets, identify dependencies, and inspect the relevant code and project instructions. Reuse context already gathered by the calling workflow. 2. Create or use the task's feature branch. Work sequentially in the current checkout, one ticket at a time. 3. Build each ticket with `jidoka-tdd` when project instructions allow test-first development; otherwise follow the project’s test approach and scope. 4. Run targeted or quick checks during iteration and fix failures, following the project's required cadence. Run the project's full verification at the point the calling workflow sets, or after the last ticket when used on its own; a missing tool or a failing check is a blocker, never something to skip. Find verification in the project's agent instructions, contributing docs or build files; if none is found, ask the user once, or report it when unattended. Reuse a passing result only while the checked code and relevant inputs are unchanged, and honor stricter project requirements. 5. Resolve each finished ticket the way the issue tracker closes work, unless the calling workflow handles that. 6. Verify the result against the spec. Report the completed work, tests added, checks performed, and any remaining blockers. Leave commits, pushing, and PR creation to the calling workflow unless the user explicitly requests them. Do not require subagents, extra worktrees, a draft PR, or a separate code review as part of this skill.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named jidoka-implement.
Database snapshot: 13.11.2026 · package version e56bef2457c6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96jidoka-implement-fast
Implement a spec and its tickets without TDD. Use for the Build stage of jidoka-fast or when implementation without TDD is requested. - 96jidoka-implement-balanced
Implement a spec and its tickets with project-directed behavior tests, without red-green cycles. Use for the Build stage of jidoka-balanced or when tested implementation without strict TDD is requested. - 86implement-spec
Implement a specification in code. Use when the user wants to implement the result of /mattpocock:to-spec and /mattpocock:to-tickets, or asks to work a whole spec on one integration branch. - 95implement
Implement a piece of work based on a spec or set of tickets. Use when an agreed spec or ticket set should now be built. Triggers on: implement, build this spec, work these tickets. - 100jidoka
Debug software by making failures visible, reproducing them, finding contributing causes, and adding durable regression protection. Use for bugs, failing tests, incidents, regressions, flaky behavior, and unexplained production errors. - 88implement
Implement a piece of work based on a spec or set of tickets. Drives TDD internally (one red-green slice at a time), runs typechecking and test suites, then closes with code-review before committing. Use when the user says "implement this", "build this feature", "code this up",…