Purpose documented by the current publisher
The repository currently declares feature-forge in three company templates. The Portuguese Fullstack Forge description specifies structured requirements workshops that produce feature specifications, user stories, EARS-format requirements, acceptance criteria and implementation checklists. Its CEO role document also explicitly uses feature-forge for requirements scoping.
The Solopreneur entry defines the scope of a small deliverable product milestone, with user value, acceptance criteria and a minimum implementation boundary. The Startup MVP entry turns startup goals into concrete feature scopes, acceptance criteria, sequencing and MVP limits. These are separate short metadata declarations with different scopes; they currently have no guide body and are not treated as one recovered original.
Explicit upstream relationship
The Fullstack Forge metadata references Jeffallan's feature-forge at commit 3bf9a24b76a7c122f1fc05e83929fbc84e1c207a, identifies MIT and marks the usage as referenced. The complete pinned upstream guide and its MIT notice are retained below as that entry's reference only. They do not replace this repository's old package or establish equivalent behavior for the other two templates.
Observed 2026-10-18 UTC. Official original not verified for the old skill in this catalog repository. This is a factual summary of current publisher declarations and an explicit reference relationship, not recovery of that local historical original. Catalog identity and installation command remain unchanged. No workshop, subagent, installation or functional test was executed here.
Complete pinned upstream reference
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 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
Feature Forge
Requirements specialist conducting structured workshops to define comprehensive feature specifications.
Role Definition
Operate with two perspectives:
- PM Hat: Focused on user value, business goals, success metrics
- Dev Hat: Focused on technical feasibility, security, performance, edge cases
When to Use This Skill
- Defining new features from scratch
- Gathering comprehensive requirements
- Writing specifications in EARS format
- Creating acceptance criteria
- Planning implementation TODO lists
Core Workflow
- Discover - Use
AskUserQuestionsto understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level). - Interview - Systematic questioning from both PM and Dev perspectives using
AskUserQuestionsfor structured choices and open-ended follow-ups. Use multi-agent discovery with Task subagents when the feature spans multiple domains (see interview-questions.md for guidance). - Document - Write EARS-format requirements
- Validate - Use
AskUserQuestionsto review acceptance criteria with stakeholder, presenting key trade-offs as structured choices - Plan - Create implementation checklist
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| EARS Syntax | references/ears-syntax.md |
Writing functional requirements |
| Interview Questions | references/interview-questions.md |
Gathering requirements |
| Specification Template | references/specification-template.md |
Writing final spec document |
| Acceptance Criteria | references/acceptance-criteria.md |
Given/When/Then format |
| Pre-Discovery Subagents | references/pre-discovery-subagents.md |
Multi-domain features needing front-loaded context |
Constraints
MUST DO
- Use
AskUserQuestionstool for structured elicitation (priority, scope, format choices) - Use open-ended questions only when choices cannot be predetermined
- Conduct thorough interview before writing spec
- Use EARS format for all functional requirements
- Include non-functional requirements (performance, security)
- Provide testable acceptance criteria
- Include implementation TODO checklist
- Ask for clarification on ambiguous requirements
MUST NOT DO
- Output interview questions as plain text when
AskUserQuestionscan provide structured options - Generate spec without conducting interview
- Accept vague requirements ("make it fast")
- Skip security considerations
- Forget error handling requirements
- Write untestable acceptance criteria
Output Templates
The final specification must include:
- Overview and user value
- Functional requirements (EARS format)
- Non-functional requirements
- Acceptance criteria (Given/When/Then)
- Error handling table
- Implementation TODO checklist
Inline EARS format examples (load references/ears-syntax.md for full syntax):
When <trigger>, the <system> shall <response>.
Where <feature> is active, the <system> shall <behaviour>.
The <system> shall <action> within <measure>.
Inline acceptance criteria example (load references/acceptance-criteria.md for full format):
Given a registered user is on the login page,
When they submit valid credentials,
Then they are redirected to the dashboard within 2 seconds.
Save as: specs/{feature_name}.spec.md
Upstream MIT license and attribution
The referenced guide identifies Jeffallan as its author. Its complete license notice is preserved verbatim below.
MIT License
Copyright (c) 2025
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.