harness-plan

Runs requirement analysis, solution design, and gate review stages to produce a vetted design verdict.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Alan-IFT/harness-kit --skill harness-plan-alan-ift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-plan
Source: https://github.com/Alan-IFT/harness-kit/tree/main/skills/harness-plan
Command: npx skills add https://github.com/Alan-IFT/harness-kit --skill harness-plan-alan-ift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing engineering time to a half-baked design is expensive. This Skill runs only the design half of the Harness 7-agent pipeline — Requirement Analyst, Solution Architect, and Gate Reviewer — and stops with a verdict before any code is written, so you can validate an architecture before building it. ## Core Features & Use Cases - Design-only pipeline: Dispatches stages 1-3 (RA, SA, GR) and produces 01_REQUIREMENT_ANALYSIS.md, 02_SOLUTION_DESIGN.md, and 03_GATE_REVIEW.md with an APPROVED / CHANGES REQUIRED / REJECTED verdict. - Resumable output: Running the full /harness pipeline later on the same task slug detects the existing 01-03 documents and skips directly to Development. - Task decomposition discipline: Splits designs into tracer-bullet vertical slices sized to fit one model reasoning window, with real consumption dependencies only. - Use Case: You have a feature idea and want an architecture review before a sprint. Run the plan mode to get a gate-reviewed design document set, then hand approved designs to the full pipeline when ready. ## Quick Start Ask the AI to run harness-plan on your feature idea to produce a requirement analysis, solution design, and gate review verdict without writing any code.

Frequently Asked Questions about harness-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a software design before writing code?▼

Run harness-plan to dispatch the Requirement Analyst, Solution Architect, and Gate Reviewer stages only. It produces three design documents and a verdict — APPROVED FOR DEVELOPMENT, CHANGES REQUIRED, or REJECTED — without invoking any Developer stage.

What is the difference between harness-plan and the full harness pipeline?▼

harness-plan runs only stages 1-3 (analysis, design, gate review) and stops before code is written, costing roughly 30-40% of the full pipeline. The full /harness pipeline continues through Developer, Code Reviewer, QA, and Delivery stages.

Can I resume development after a harness-plan design is approved?▼

Yes. Running /harness on the same task slug detects the existing 01-03 documents and skips those stages, jumping directly to Development. The mode choice is recorded in PM_LOG.md so the full pipeline knows the design was pre-vetted.

When should I not use design-only pipeline mode?▼

Skip it when the task is small enough that design overhead exceeds implementation, when acceptance criteria are already obvious, or when you actually want code written. In those cases use a direct edit or the full /harness pipeline instead.

How should large designs be split into tasks?▼

Split into tracer-bullet vertical slices that cut end-to-end through every layer the change touches and are independently verifiable. Size each task to fit one model reasoning window (roughly 120k tokens) and declare only real consumption dependencies between tasks.