speckit-companion-specify

Generates prioritized feature specifications with user stories, requirements, and quality checklists.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-specify-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-specify
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-companion-specify
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-specify-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a feature specification that is complete, testable, and free of implementation detail is slow and error-prone, and teams often skip quality checks or mix planning into specs. This Skill automates the specify phase of the spec-kit Companion pipeline, producing a structured spec.md that downstream plan, tasks, and implement steps can consume directly. ## Core Features & Use Cases - Prioritized User Stories: Drafts P1-P3 user stories with acceptance scenarios, edge cases, functional requirements (FR-001...), key entities, and measurable success criteria. - Quality Checklist: Writes a requirements checklist and runs a self-check pass, leaving genuine ambiguities as [NEEDS CLARIFICATION] markers for the clarify step. - Size Classification & Fast-Track: Classifies the change as simple, normal, or oversized; simple changes get a lean plan.md pointer and a real tasks.md checklist so they can skip straight to implement. - Use Case: A developer in a spec-kit project describes a new feature; the Skill mints a numbered specs/ directory, loads relevant living specs, writes spec.md plus checklists/requirements.md, records lifecycle timing, and hands off to the next pipeline step. ## Quick Start Run the companion specify command with a feature description to generate a prioritized spec.md and requirements checklist in a new specs directory.

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 specs directory, writes spec.md with prioritized user stories and functional requirements, and adds a requirements quality checklist.

What sections does a spec-kit spec.md file contain?▼

A spec.md contains User Scenarios and Testing with prioritized stories, Edge Cases, Functional Requirements, Key Entities, Success Criteria with measurable outcomes, Assumptions, and optionally Verbatim Constraints for exact identifiers the user pinned.

Does the specify step require a spec-kit project structure?▼

Yes, it requires a spec-kit project with a .specify directory. The Skill reads .specify/feature.json, extension hooks in extensions.yml, and companion scripts under .specify/extensions/companion/scripts.

When does a change skip the plan and tasks steps?▼

Changes classified as simple, meaning roughly five or fewer files and ten or fewer tasks, fast-track to implement. The Skill writes an Approach section in spec.md, a pointer plan.md, and a real tasks.md checklist, then folds the plan and tasks lifecycle steps.

Why are NEEDS CLARIFICATION markers limited to three?▼

The limit forces informed defaults instead of unresolved guesses, keeping specs actionable. Genuine ambiguities stay as markers and are deferred to the separate clarify step rather than blocking specification.