Feature Forge — сбор требований и спецификация фичи

documentation

Feature Forge is a Claude Code skill that runs structured requirements workshops and produces a complete feature specification: user stories, EARS-format functional requirements, acceptance criteria, and an implementation TODO checklist. Reach for it when a new feature needs to be defined from scratch before a single line of code is written, when stakeholders and developers can't agree on what "done" looks like, when requirements are vague and keep shifting, or when you need a testable PRD that QA can actually use. The skill operates from two simultaneous perspectives — PM Hat (user value, business goals, success metrics) and Dev Hat (technical feasibility, security, performance, edge cases). The workflow follows five phases: Discover, Interview, Document, Validate, Plan; multi-domain features trigger pre-discovery subagents for front-loaded context. All functional requirements are written in EARS syntax, acceptance criteria in Given/When/Then format, and the final document is saved to specs/{feature_name}.spec.md. MIT licence, authored by jeffallan. Direction is forward — producing a spec before development starts — not reverse-engineering documentation from existing code (use spec-miner for that). Works inside Claude Code; it does not replace team-wide requirements-management platforms like Jira or Confluence when cross-team traceability is needed.