Feature Forge
技能 已验证 活跃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.
To streamline the process of defining new features by systematically gathering comprehensive requirements and producing detailed specifications.
功能
- Conducts structured requirements workshops
- Produces feature specifications and user stories
- Generates EARS-format functional requirements
- Defines testable acceptance criteria
- Creates implementation checklists
使用场景
- Defining new features from scratch
- Gathering comprehensive requirements
- Writing specifications in EARS format
- Planning implementation tasks
非目标
- Generating code directly
- Managing project timelines
- Performing technical architecture design beyond requirement feasibility
Compliance
- info:GDPRThe skill elicits requirements but does not directly operate on personal data; however, LLM interaction means personal data may be submitted.
Practical Utility
- info:Edge casesThe `interview-questions.md` covers edge cases and failure modes from a PM and Dev perspective, but a formal documented list within the SKILL.md might be more robust.
安装
请先添加 Marketplace
/plugin marketplace add jeffallan/claude-skills/plugin install claude-skills@fullstack-dev-skills质量评分
已验证类似扩展
Add New Opc Skill
100Checklist and automation guide for adding a new skill to the OPC Skills project. Ensures all required files, metadata, logos, and listings are created before release. Use when adding a new skill, publishing a skill, or preparing a skill for release.
Ce Brainstorm
100Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
Deep Dive
992-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection
Acceptance Criteria Generator
99Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
Pm Prd
98Generate a Product Requirements Document (PRD) with four modes: Full PRD for net-new features, Lightweight Feature Spec for sprint-level work, Iteration/V2 Spec for follow-ups on shipped features, and Migration/Compliance Spec for regulatory or API migrations. Enforces problem-first thinking, leading + lagging metrics, non-goals, and testable acceptance criteria. Use when someone says "PRD", "product requirements", "feature spec", "write a spec", "requirements document", "what to build", "engineering spec", "technical requirements", "migration spec", "compliance spec", "V2 spec", or "iteration spec".
Agent Specification
95Agent skill for specification - invoke with $agent-specification