Execution Workflow GitHub MIT

GitHub Spec-Kit

Spec-first toolkit ("Specify") that drives any AI coding agent from a natural-language feature description through specification, planning, and task breakdown to implementation. Spans its own requirements and design, but in the ProductBuildersHQ system the definition-side spec feeds its /speckit.specify step.

Repository Documentation

Detection

A project uses Spec-Kit when any of these exist:

.specify/
.specify/memory/
.specify/templates/
specs/*/spec.md

Status Model

Method: task-checkboxes

Percent complete = checked over total checkbox lines in tasks.md ("- [X]" or "- [x]" vs "- [ ]"). Phase is also inferable from which artifacts exist: spec only → specified; +plan → planned; +tasks → ready to implement.

Lifecycle

1

Constitution /speckit.constitution

Establish project governing principles.
2

Specify /speckit.specify

Turn a feature description into a structured specification.
3

Clarify /speckit.clarify

Resolve open questions in the spec (recommended before planning).
4

Plan /speckit.plan

Produce the implementation plan and Phase 0/1 design docs.
5

Tasks /speckit.tasks

Break the plan into an ordered task list.
6

Analyze /speckit.analyze

Cross-artifact consistency check before implementation.
7

Implement /speckit.implement

Execute tasks, writing code and marking tasks complete.

On-Disk Artifacts

.specify/memory/constitution.md constitution Project governing principles, ratified and versioned.

.specify/feature.json config Active feature pointer: {"feature_directory": "specs/NNN-..."}.

specs/<NNN-feature>/spec.md requirement Feature specification (WHAT/WHY) — user stories, FR-###, SC-### success criteria. Maps to PRD.

specs/<NNN-feature>/plan.md design Implementation plan (HOW) — technical context and Constitution Check gate. Maps to TRD.

specs/<NNN-feature>/research.md research Phase 0 decisions, rationale, and alternatives.

specs/<NNN-feature>/data-model.md design Entities, fields, relationships, and state transitions.

specs/<NNN-feature>/contracts/ contract API/interface contracts (directory; may be absent for internal-only work).

specs/<NNN-feature>/tasks.md tasks Ordered, checkboxed task list grouped by phase and user story. Maps to PLAN.

src/ output Source code and tests written during implementation.

Fed by Definition Workflows

PBHQ Lite → Spec-Kit A lightweight PBHQ Lite definition produces a reconciled spec; Spec-Kit's /speckit.specify consumes it (or it is merged into specs/<feature>/spec.md), after which plan → tasks → implement proceeds.