application-implementation-workflow
implement-workflow
Shorthand: implement-workflow. Govern the application implementation lifecycle with scoped Agent #1 implementation, independent Agent #2 review, coherent issue-bound corrections, issue-recorded Agent #2 implementation review as the authoritative review record, a supplemental role-based Agent #2 PR review only when its triggers apply, optional automated review input, Agent #2-owned correction approval, and boring promotion. Inspect existing architecture before inventing new structures, ask when material requirements are ambiguous, and use the three-question review contract without expanding work into unrelated application auditing.
- Technician role
- implementer
Technical details
- Source revision
- v0.1.0 · db2fcac
- Files
- SKILL.md, templates, templates/issue.md
Download the ZIP below, preserve the application-implementation-workflow/ directory, and place it in a skill directory supported by your harness.
Hand-placed skills are unmanaged. Canonical skills resolve project choices through garage config validate, so configuration-dependent steps still need a valid project configuration and garage on PATH. Directly requested discovery does not require configuration for its discovery-applicability decision.
From a project with valid configuration and declared skill targets, install and verify the complete embedded canonical skill set, together with the manuals the project adopts:
garage config validate garage skills install garage skills verify
The CLI supports user-scope targets for Claude Code, Codex, and Copilot CLI, not individual-skill or project-scope installs. Harness path behavior was confirmed on macOS; Linux and Windows harness behavior remains unconfirmed. Existing unmanaged or modified copies require explicit replacement consent and a backup. See skill installation.
