What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
- files
- 6
- Markdown files
- 6
- scripts
- 0
- references
- 5
- Size
- 19.8 KB
- Structural complexity
- Low
File inventory
PathTypeBytes
skills/feature-forge/references/acceptance-criteria.mdReference2.9 KB
skills/feature-forge/references/ears-syntax.mdReference2.6 KB
skills/feature-forge/references/interview-questions.mdReference5.4 KB
skills/feature-forge/references/pre-discovery-subagents.mdReference2 KB
skills/feature-forge/references/specification-template.mdReference2.5 KB
skills/feature-forge/SKILL.mdInstruction4.4 KB
SKILL.md frontmatter
{
"name": "feature-forge",
"description": "Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.",
"license": "MIT",
"metadata": {
"author": "https://github.com/Jeffallan",
"company": "https://synergetic.solutions",
"version": "1.1.0",
"domain": "workflow",
"triggers": "requirements, specification, feature definition, user stories, EARS, planning",
"role": "specialist",
"scope": "design",
"output-format": "document",
"related-skills": "fullstack-guardian, spec-miner, test-master"
}
}