spec-writer

Guide interactive sessions to draft approved spec.md files.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/gaabscps/ai-squad --skill spec-writer-gaabscps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/gaabscps/ai-squad/tree/main/squads/sdd/skills/spec-writer
Command: npx skills add https://github.com/gaabscps/ai-squad --skill spec-writer-gaabscps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn fuzzy feature pitches into a concrete, approved Spec by managing a structured, interactive session lifecycle and capturing decisions in a shareable spec.

Core Features & Use Cases

  • Interactive session creation and spec_id generation for new features.
  • Mandatory intent collection: planned_phases, pipeline_mode, output_locale, saved to session.yml.
  • Draft and refine spec.md with NEEDS CLARIFICATION markers when ambiguous, and support resumption via FEAT-NNN.
  • PM-bypass integration with a formal bypass gate and corresponding pm_decision evidence.
  • Auto-advance to the next Phase after approval, enabling seamless handoff to Plan/Tasks/Implementation phases.

Quick Start

Start a fresh spec with /spec-writer, or resume with /spec-writer FEAT-NNN, and follow the interactive prompts to generate the initial spec draft.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I turn a feature pitch into an approved spec?▼

To turn a feature pitch into an approved spec, start an interactive session to collect mandatory intent like planned_phases, pipeline_mode, and output_locale, then draft a structured spec.md with explicit approval gating before advancing.

Can I resume a spec writing session if I stop halfway?▼

Yes, you can resume a spec writing session by invoking the tool with your existing FEAT-NNN identifier, which loads your saved session.yml state to continue interactive prompts and refine the draft spec.md.

What happens to ambiguous requirements during spec generation?▼

When spec generation encounters ambiguous requirements, it automatically inserts NEEDS CLARIFICATION markers directly into the spec.md draft, ensuring unresolved details are visibly flagged for review before final approval.

How do I bypass the PM approval gate for a feature spec?▼

To bypass the PM approval gate for a feature spec, you must trigger the formal bypass mechanism and record the corresponding pm_decision evidence within the session, ensuring the spec workflow maintains an auditable trail.

Does the spec workflow auto-advance to the implementation phase?▼

Yes, the spec workflow auto-advances to the next phase, such as Plan or Tasks, immediately after explicit approval is granted, enabling a seamless handoff for subsequent implementation lifecycle stages.