← ClaudeAtlas

ai-software-delivery-workflowlisted

Use turn-based Planner, Verifier, Implementer, and Tester roles to ship one feature at a time, then generate a goal-based verification handoff for final completion audit. This skill is agent-agnostic: read the referenced files and follow the contract directly without installing an npm package or plugin.
Stephen-Kimoi/ai-software-delivery-workflow · ★ 0 · AI & Automation · score 70
Install: claude install-skill Stephen-Kimoi/ai-software-delivery-workflow
# AI Software Delivery Workflow Use this skill when a requester asks an agent to plan, implement, and verify a feature with separate planning, review, implementation, and testing responsibilities. The workflow combines two loop types: ```text Turn-based workflow = controlled implementation loop Goal-based loop = completion and verification loop ``` Do not treat `/goal` as a replacement for the four roles. Treat it as the handoff after the Tester finishes, when the user needs a final autonomous audit against a clear finish line. ## Read First Before starting work, read these files in order: 1. `references/role-contract.md` 2. `references/feature-tracking.md` 3. `references/verification-harness.md` 4. `references/goal-verification-handoff.md` 5. `references/evidence-driven-testing.md` when the feature changes UI behavior 6. The target repository's `feature_list.json`, `AGENTS.md` or equivalent agent instructions, and `DECISIONS.md` or equivalent decision log If a referenced file is missing in the target repository, create the smallest compatible file needed for the workflow instead of stopping. ## Workflow Run the feature through these roles in sequence: 1. **Planner:** read real source files and produce a locked design. 2. **Verifier:** independently check the plan for missing facts, vague checks, bad assumptions, and untestable claims. Loop back to Planner until the plan is executable or blocked. 3. **Implementer:** make the smallest code and test changes tha