speckit-companion-specify

Generates prioritized feature specifications with user stories, requirements, and quality checklists for spec-kit projects.

Updated May 28, 2026
One-click install
npx skills add https://github.com/whw23/PingoGate --skill speckit-companion-specify-whw23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-specify
Source: https://github.com/whw23/PingoGate/tree/main/.claude/skills/speckit-companion-specify
Command: npx skills add https://github.com/whw23/PingoGate --skill speckit-companion-specify-whw23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a feature specification that is business-readable, testable, and ready for downstream planning is slow and inconsistent. This Skill automates the specify phase of a spec-kit Companion pipeline, producing a structured spec.md with prioritized user stories, functional requirements, and measurable success criteria. ## Core Features & Use Cases - Structured Spec Generation: Creates spec.md with prioritized user stories (P1-P3), acceptance scenarios, functional requirements, edge cases, key entities, and measurable success criteria. - Size Classification & Fast-Track: Classifies the change as simple, normal, or oversized using a 5-file/10-task guardrail, and fast-tracks small changes by emitting lean plan.md and tasks.md files inline. - Quality Checklist & Lifecycle Tracking: Writes a requirements quality checklist, runs a self-check pass, and records step timing via the Companion write-context.py script. - Use Case: A developer in a spec-kit project describes a new feature; the Skill mints a numbered specs/ directory, writes a stakeholder-ready spec.md, validates it against a checklist, and hands off to the plan step. ## Quick Start Ask the assistant to run the Companion specify step for your feature idea, for example: create a specification for adding user notification preferences to the settings page.

Frequently Asked Questions about speckit-companion-specify

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

FAQPage Schema
How do I generate a feature specification with spec-kit Companion?▼

Run the Companion specify command with a feature description. It creates a numbered directory under specs/, writes spec.md with prioritized user stories and requirements, and adds a quality checklist before handing off to the plan step.

What sections does a spec-kit specification contain?▼

The spec includes User Scenarios and Testing with prioritized P1-P3 stories, Edge Cases, Functional Requirements as numbered FR statements, Key Entities, measurable Success Criteria, Assumptions, and optional Verbatim Constraints for exact identifiers.

Does Companion specify require an existing spec-kit project?▼

Yes. It requires a spec-kit project structure with a .specify directory, since it reads .specify/feature.json, runs extension hooks from .specify/extensions.yml, and records timing through the Companion write-context.py script.

When does Companion fast-track a change past plan and tasks?▼

A change is fast-tracked when it is classified as simple, meaning it plausibly touches five or fewer files and decomposes into ten or fewer tasks without larger scope signals. Simple changes get an inline Approach section plus lean plan.md and tasks.md files.

Why does specify refuse to write into an existing spec directory?▼

The .specify/feature.json file points at the previous spec, which is often already completed. Reusing that directory would clobber finished work, so the command always mints a fresh numbered directory unless a target path is explicitly given.