Idea Assessment Pipeline Extension

A five-stage assessment pipeline for Spec Kit that turns any idea into a defensible go / needs-clarification / kill decision before it enters Spec-Driven Development. It is the missing discovery track that sits in front of the SDD delivery track (specify → clarify → plan → tasks → analyze → implement).

Discovery answers "is this worth building?" Delivery answers "how do we build it?" Only ideas that survive assessment hand off to /speckit.specify.

Overview

Each idea lives in its own directory under .specify/assessments/<slug>/, with one Markdown artifact per stage:

.specify/assessments/<slug>/
├── intake.md      # speckit.assess.intake   — capture the raw idea
├── research.md    # speckit.assess.research — gather (and challenge with) evidence
├── problem.md     # speckit.assess.define   — define the problem, goals, metrics
├── concept.md     # speckit.assess.shape    — shape solution options + appetite
└── decision.md    # speckit.assess.decide   — go / needs-clarification / kill → handoff

The pipeline is a funnel: most ideas should be killed or parked before shape. Killing an idea with a documented reason is a successful outcome, not a failure.

flowchart LR
    A[intake] --> R[research] --> D[define] --> S[shape] --> C{decide}
    C -->|go| SPEC[/speckit.specify/]
    C -->|kill| X[closed, recorded]
    C -.->|needs-clarification: revisit the named earlier stage| A

Commands

Stages are meant to run in order but are not rigidly gated:

• define is the minimum viable stage and can run directly on user input (intake/research optional).
• shape requires problem.md.
• decide requires problem.md; a go verdict expects concept.md (otherwise it is downgraded to needs-clarification).

Slug Conventions

A slug is the per-idea directory name under .specify/assessments/. It is the handle all five commands share.

• User-provided: normalized to lowercase kebab-case (e.g. offline-mode, cut-onboarding-friction). Preserved verbatim after normalization — no timestamps or numbers appended.
• Asked for: in interactive use, speckit.assess.intake asks for a slug when none is supplied, suggesting a kebab-case default derived from the idea.
• Automated: when no human is available, the agent generates a unique slug and never overwrites an existing assessment directory (appending -2, -3, … or a short date as needed).
• Reuse from context: later stages reuse the slug reported earlier in the same session, confirmed by the presence of the assessment directory.

Installation

specify extension add assess

Disabling

specify extension disable assess
specify extension enable assess

Typical Flow

# 1. Capture an idea (pasted text, a URL, or "assess this repo")
/speckit.assess.intake "Let users work offline and sync when they reconnect" slug=offline-mode

# 2. Gather evidence — and reasons it might not be worth it
/speckit.assess.research slug=offline-mode

# 3. Define the actual problem
/speckit.assess.define slug=offline-mode

# 4. Shape 2–3 concept options with appetites
/speckit.assess.shape slug=offline-mode

# 5. Decide — go, clarify, or kill
/speckit.assess.decide slug=offline-mode
# → on "go", hand the decision.md handoff summary to /speckit.specify

Handoff

assess is a standalone pipeline you enter deliberately — it registers no lifecycle hooks and never inserts itself into /speckit.specify. The only coupling runs forward and by choice: a go verdict from /speckit.assess.decide hands its decision.md summary to /speckit.specify. Discovery and specification stay separate processes.

Guardrails

• Only speckit.assess.* commands write, and only inside .specify/assessments/<slug>/. None of them modify source code — solution design and implementation belong to the SDD lifecycle (/speckit.specify onward).
• Web content fetched during intake/research is treated as untrusted data, governed by an explicit URL Trust Policy (allowlisted public sources fetched freely; unknown hosts prompted or skipped; loopback/RFC1918/metadata endpoints refused).
• Evidence is never over-claimed: unsourced statements are tagged ASSUMPTION, and research.md always includes an Evidence Against the Idea section.
• Verdicts are never over-claimed: a go requires a valid problem, adequate+ evidence (never weak/unknown), and a shaped concept; otherwise the honest verdict is needs-clarification.
• Slugs are normalized to [a-z0-9-] and an empty result is rejected; before any read or write, each command also rejects symlinked path components and verifies the resolved path stays inside the project root — so an assessment can never escape .specify/assessments/, even in a crafted or cloned project.
• No command overwrites an existing artifact without confirmation; in automated mode it refuses.

Relationship to Other Extensions

assess is deliberately the generic, role-neutral discovery track — usable by a founder, PM, BA, engineer, or designer. Richer or more specialized pre-SDD flows in the community catalog (e.g. product-lifecycle orchestrators, technical-discovery, intake-normalization, brownfield onboarding) can layer on top of or feed into it; assess aims to be the minimal, opinionated funnel that ends cleanly at the /speckit.specify handoff.