skills.rest
cjrain-12505614
cjrain-12505614COMMUNITY
Explore all skills by this author →
GitHub

solo-feature-planning

Generates structured feature specification documents with user stories, acceptance criteria, data models, and API definitions.

Updated Apr 23, 2026
Search Tags:#api design#requirements#acceptance criteria#user stories#data model#product planning#feature spec
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-feature-planning-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-feature-planning
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-feature-planning
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-feature-planning-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague business requirements into complete, consistent feature specification documents is time-consuming and error-prone for solo developers. This Skill standardizes the entire planning output so every feature spec follows the same template and quality bar. ## Core Features & Use Cases - Full Spec Template: Generates feature specs covering overview, user stories, Gherkin acceptance criteria, screen inventory, data models, REST API endpoints, edge cases, and performance considerations. - Versioned Document Workflow: Saves specs as feature_spec_{name}_{version}.md in docs/02_기획/ with Draft/Review/Approved status tracking and version promotion rules. - Traceability Linking: Connects specs to requirements (REQ-XX), decisions (D-XX), and phases, and hands off to downstream artifacts like QA scenarios, wireframes, and DB schemas. - Use Case: Ask to plan an authentication feature and receive a complete spec with user stories, acceptance criteria, User/EmailVerification data models, and signup/verify-email API contracts. ## Quick Start Ask the assistant to write a feature spec for the authentication feature using this skill.

Frequently Asked Questions about solo-feature-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a feature specification document?▼

Request a feature spec by name and the skill generates a complete document covering overview, user stories, acceptance criteria, screens, data models, and APIs. The output is saved as feature_spec_{name}_{version}.md in the docs/02_기획/ folder.

What should a feature spec template include?▼

This template includes business goals, scope, user stories with priorities, Gherkin acceptance criteria, a screen inventory table, entity definitions with ERD, REST API request/response examples, edge cases, performance targets, and a glossary.

How are acceptance criteria written in this skill?▼

Acceptance criteria use Gherkin Given/When/Then syntax, with at least three criteria per user story covering normal flows, validation errors, and boundary conditions. Each criterion is numbered and mapped to its parent story ID.

How does spec versioning work for feature documents?▼

Specs start at v0.1 as Draft and increment through internal feedback rounds until PM approval promotes them to v1.0. Status values are Draft, Review, and Approved, and changes are recorded in the decision log.

Can I generate only part of a feature spec?▼

Yes, you can request specific sections such as only user stories or only the data model for a feature. The skill focuses on the requested section of the template rather than producing the full document.

Related Skills

Explore More Product & Management Skills→
EMSEROEMSERO

spec-engineer

Convert interactive requirements into a structured markdown specification document.

Official
Advanced
jeremy-newhousejeremy-newhouse

wa:dev-plan

Generate dependency-aware implementation task plans from FRD acceptance criteria.

Community
Advanced
wildbitcawildbitca
1

common-product-requirements

Guide iterative discovery and document product requirements into a PRD file.

Official
Advanced
striderZAstriderZA
72

quick-design

Generate lightweight design specifications for small game changes with acceptance criteria.

Community
Intermediate