spec

Generate SPEC.md and HANDOFF.md documents from approved Phase 1 research.

3|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/wilsonkichoi/agentic_development_workflow --skill spec-wilsonkichoi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/wilsonkichoi/agentic_development_workflow/tree/main/skills/spec
Command: npx skills add https://github.com/wilsonkichoi/agentic_development_workflow --skill spec-wilsonkichoi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts Phase 1 research into a clear, implementation-ready specification and handoff materials so engineering teams can build reliably without ambiguity, rework, or lost context.

Core Features & Use Cases

  • Specification Generation: Produces SPEC.md with prioritized milestones, system architecture, database schemas, API contracts, diagrams, and non-functional requirements.
  • Handoff & Execution Planning: Creates HANDOFF.md with milestone ordering, execution sequence, acceptance criteria, and known risks to enable Phase 4 implementation.
  • Review & Governance: Produces RFC summaries and decision records, enforces plan/read-only mode, and pauses for human review to ensure alignment before coding begins.
  • Use Case: Ideal for teams transitioning from research to engineering handoff who need formalized specs, CI/CD and environment setup guidance, and explicit acceptance criteria.

Quick Start

Generate a complete SPEC.md and HANDOFF.md from the files under workflow/research/final and stop for human review.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I generate a software specification and handoff document from research inputs?▼

To generate a software specification and handoff document, you apply specification tasks to approved Phase 1 research files, producing a SPEC.md and HANDOFF.md with prioritized milestones, system architecture, and acceptance criteria.

What is the best way to define system architecture and database schemas for engineering handoff?▼

Defining system architecture and database schemas for handoff requires generating comprehensive specifications that include SQL schemas, OpenAPI-style API contracts, and Mermaid diagrams to ensure engineering teams build without ambiguity.

Can I create OpenAPI-style API contracts and architecture diagrams from approved research?▼

Yes, you can create OpenAPI-style API contracts and architecture diagrams by processing approved research inputs to produce formal specification documents that enforce development environment setup and explicit non-functional requirements.

How do I enforce human review gates before coding begins?▼

To enforce human review gates before coding begins, the specification process enforces a read-only mode that pauses for human alignment after generating RFC summaries, decision records, and milestone execution sequences.

Does this specification process support CI/CD and development environment setup guidance?▼

Yes, this specification process supports CI/CD and development environment setup guidance by generating handoff materials that include execution sequences, known risks, and acceptance criteria for Phase 4 implementation.

When do I need RFC summaries and decision records for software milestones?▼

You need RFC summaries and decision records for software milestones when transitioning from Phase 1 research to engineering handoff, ensuring formalized specs and explicit acceptance criteria are established before implementation.