Define end-to-end feature specifications from discovery to planning.
npx skills add https://github.com/nkseth/copilot-dev-skills --skill feature-forge-nkseth
Please help me install this Agent Skill. Skill: feature-forge Source: https://github.com/nkseth/copilot-dev-skills/tree/main/skills/feature-forge Command: npx skills add https://github.com/nkseth/copilot-dev-skills --skill feature-forge-nkseth
This skill helps product teams move from vague ideas to concrete, testable feature specifications by guiding structured discovery, documentation, and planning.
Initiate a structured workshop to define a new feature and generate the accompanying specification artifacts.
High-intent search queries and answers about installing and using this skill.
Feature specifications are generated from requirements workshops by guiding structured discovery to clarify goals, target users, success metrics, and scope, then producing testable documentation artifacts like PRDs and implementation checklists.
EARS format is a structured syntax for writing requirements that produces testable user stories and acceptance criteria. It is applied during feature specification to ensure documentation is unambiguous and verifiable for development teams.
Vague product ideas are transformed into concrete user stories through structured discovery workshops that define scope and success metrics. The workflow then generates user stories, EARS requirements, and acceptance criteria for cross-team alignment.
Yes, non-functional requirements and implementation checklists are generated alongside functional specifications. The workflow satisfies documentation templates by balancing value, feasibility, security, and performance considerations for product and development roles.
The best way to structure feature planning is using an end-to-end specification workflow from discovery to planning. This generates output-ready artifacts for roadmaps and PRDs, ensuring cross-team alignment through role-based guidance for PMs and developers.
No prior documentation templates are needed to start a feature specification workflow. The structured discovery process guides the creation of feature specifications, user stories, and implementation checklists from initial vague ideas without requiring pre-existing formats.
pingmepiGenerate a structured 7-section product brief from a business statement.
xloxn69Convert feature descriptions into structured user stories with acceptance criteria.
dieu-donneeIdentify feature requirements and produce structured EARS specifications, acceptance criteria, and implementation checklists.
getcrew44Generate an eight-phase PRD with problem statements, personas, success metrics, and user stories.
