k1nak0/implementation-workflow
A multi-agent implementation pipeline that takes a GitHub Map Issue task (or a standalone requirement) through user scrutiny, optional Issue refinement, codebase investigation, planning, a human-approved test-first specification (automated tests plus committed manual test procedures), implementation against frozen tests, automated and human review, history cleanup, and PR.
Synthesise requirements, codebase analysis, and library research into a concrete implementation plan that splits every acceptance criterion into automated test cases and manual test steps, plus a CI readiness check and a documentation update plan. Runs inline (not as an isolated agent) so it can ask the user directly when the test strategy can't be inferred. Posts the plan to the Task Issue (or creates a standalone Issue) via gh. Use for Phase 6, after Phases 1-5 have completed.
Main entry point for implementation-workflow. Takes a task off a GitHub Map Issue (or a standalone requirement) through user scrutiny, optional Issue refinement, codebase investigation, planning, human-approved test-first specification, implementation against frozen tests, automated and human review, history cleanup, and PR. Invoke this skill to implement a task, or to resume one within the same session.
Runs when the user rejects a task's content at the Phase 1 scrutiny gate. Talks the change through with the user, then rewrites the Task Issue, updates every Issue and Map Issue row the change affects, and brings the docs/design/ documents back in line — shipping the doc changes as their own PR. Use for Phase 2 of implementation-workflow, only on a needs-refinement verdict.
Set up a project to use implementation-workflow — verifies gh CLI/GitHub remote prerequisites, reports CI and docs/adr readiness, checks for a root AGENTS.md, and creates, updates, or migrates the project's docs/tools/ directory. Run once when adopting the plugin in a new project, or whenever project tooling changes. Not part of the fourteen-phase pipeline; user-invoked directly.
Establish what to implement this run — let the user choose a task from a GitHub Map Issue (or interview them for a standalone requirement), then put the task's content in front of them for scrutiny before any work starts. Returns a verdict of ready or needs-refinement. Writes requirements-report.md. Use for Phase 1 of implementation-workflow, at the start of every run.