Transform user requirements into review-ready specification checkpoints.
npx skills add https://github.com/overthestream/agent-dotfile --skill specify-overthestream
Please help me install this Agent Skill. Skill: specify Source: https://github.com/overthestream/agent-dotfile/tree/main/claude/skills/specify Command: npx skills add https://github.com/overthestream/agent-dotfile --skill specify-overthestream
This skill helps teams systematically transform user needs into well-defined specifications before coding, preventing scope creep and miscommunication.
Provide a feature description to start the specify workflow and generate a ready-to-review checkpoint.
High-intent search queries and answers about installing and using this skill.
To turn user requirements into formal specifications, provide a feature description to trigger the specify workflow, which extracts requirements, aligns terminology, and generates a review-ready checkpoint at docs/.checkpoints/{feature}/specify.md.
The best way to prevent scope creep during feature planning is to generate structured specifications with success criteria, constraints, and user flow diagrams before implementation, ensuring all stakeholders review a formal TL;DR summary.
To create a structured checkpoint for a new feature design, input the user needs to automatically generate a one-line summary, a TL;DR table, user scenarios, and references to related features saved directly at docs/.checkpoints/{feature}/specify.md.
Yes, this specification workflow supports modifying existing features by guiding requirement extraction, terminology alignment, and checkpoint creation for both new features and modifications to current implementations.
The generated feature specification uses a human-readable format featuring a one-line summary, a TL;DR table, and user flow diagrams, designed specifically to facilitate stakeholder review and clarify miscommunications.
You need to use the clarify workflow for requirements gathering after generating the initial checkpoint, allowing stakeholders to resolve ambiguities, align terminology, and refine user scenarios before finalizing the plan-ready specification.
runecalico-aiInitiate a new change and scaffold its directory in OpenSpec.
duongdevDetect and apply the correct project context for CCPM commands.
nmoralescyberConvert vague ideas into structured Spec documents with goals and acceptance criteria.
GACLoveDraft stakeholder updates with audience-specific templates for executives, engineering, customers, and partners.
