Generate a complete spec document from .claude/input/ requirements.
npx skills add https://github.com/dixus/claudeframework --skill 0-spec
Please help me install this Agent Skill. Skill: 0_spec Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/0_spec Command: npx skills add https://github.com/dixus/claudeframework --skill 0-spec
Requirements are frequently unclear when starting a feature, leading to misalignment, rework, and integration issues. This Skill generates a structured, comprehensive spec from raw inputs to ensure everyone shares a single, verifiable plan before implementation.
.claude/specs/<feature-name>.md that can be used to drive /1_implement and the rest of the pipeline.Provide a detailed or structured spec for the feature described in .claude/input/, then save it to .claude/specs/<kebab-case-feature-name>.md.
High-intent search queries and answers about installing and using this skill.
Feature requirements are transformed into a concrete specification document by reading inputs from the .claude/input/ folder and generating a structured spec with goals, scope, affected files, and validation criteria. This ensures a shared, verifiable plan before implementation begins.
A feature specification should include goals, requirements, out of scope items, affected files, new files, patterns to mirror, implementation notes, UX concepts, validation criteria, and test cases. Surfacing ambiguities and raising clarifying questions also prevents misalignment and rework.
You generate a production-ready spec for Claude feature development by placing raw requirement inputs into the .claude/input/ directory. The tool processes these inputs to produce a save-ready document at .claude/specs/<feature-name>.md that drives the implementation pipeline.
Yes, this specification generation approach operates within standalone feature development. It handles context and input folder contents to produce a comprehensive, reproducible spec document containing a defined 'Affected files' list and a 'Decisions made by Claude' section.
The best way to structure requirements before implementation is to create a comprehensive spec document that defines goals, scope, and test cases. Raising targeted clarifying questions resolves requirement gaps, ensuring everyone shares a single, verifiable plan.
Automated feature spec generation relies entirely on the quality of raw inputs provided in the .claude/input/ folder. It cannot infer missing context outside its standalone feature development scope, requiring users to resolve ambiguities through targeted clarifying questions.
ZTE-AICloudFormalize system-level requirement changes as INSERT, MODIFY, DELETE, or REFER actions.
nbarthelemyConduct project specification interviews and generate a complete SPEC.md.
haposoftAutomate implementation of approved software specification tasks with design context.
decebalStandardize feature specification writing with PRD structure and governance.