What problem does it solve? Shipping real code changes with AI often lacks structure: requirements get skipped, designs go unreviewed, and code ships untested. This Skill enforces a disciplined 7-stage pipeline so every non-trivial task passes through requirement analysis, design, gate review, development, code review, QA, and delivery before it is declared done. ## Core Features & Use Cases - Full 7-Stage Pipeline: Routes a task through Requirement Analyst, Solution Architect, Gate Reviewer, Developer, Code Reviewer, QA Tester, and Delivery, each producing a numbered stage document in docs/features/<task-slug>/. - Verify Gate and Archival: A task is not done until .harness/scripts/verify_all passes, after which archive-task harvests insights and moves stage docs to the archive. - Resume and Mode Routing: Skips stages 4-6 when a prior /harness-plan run already produced approved 01-03 documents, and redirects research, design-vetting, or open-ended tasks to the lighter /harness-explore, /harness-plan, and /harness-goal modes. - Use Case: You describe "Add a CSV export button to the orders page" and the pipeline produces requirement, design, review, development, and test documents, then ships verified code. ## Quick Start Run /harness with a clear feature, bug fix, or refactor request such as "fix the race condition in the payment retry" and let the pipeline ship it.