feature-forge

Structured requirements workshops that produce EARS-format specifications, user stories, acceptance criteria, and implementation checklists. Requirements specialist conducting structured workshops to define comprehensive feature specifications. Operate with two perspectives: Load detailed guidance based on context: The final specification must include: Inline EARS format examples (load references/ears-syntax.md for full syntax): Inline acceptance criteria example (load references/acceptance-criteria.md for full format): Save as: specs/{feature_name}.spec.md Documentation - Conducts systematic discovery interviews from both product and engineering perspectives, using structured questioning to elicit requirements before writing specifications - Outputs comprehensive specifications including functional requirements in EARS format, non-functional requirements, Given/When/Then acceptance criteria, error handling tables, and implementation TODO checklists - Supports multi-domain features through pre-discovery subagent coordination and includes reference guides for EARS syntax, interview patterns, and specification templates - Enforces testable, unambiguous requirements and security considerations throughout the workshop process - PM Hat : Focused on user value, business goals, success metrics - Dev Hat : Focused on technical feasibility, security, performance, edge cases - Defining...