skills.rest
rachel353
rachel353COMMUNITY
Explore all skills by this author →
GitHub

feature-spec

Compile feature scope and execution plans from project docs into a markdown file.

Updated Apr 7, 2026
Search Tags:#planning#architecture#frontend#traceability#docs#feature
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill feature-spec-rachel353
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/feature-spec
Command: npx skills add https://github.com/rachel353/fullty-plan --skill feature-spec-rachel353

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps frontend teams assemble a concise, source-backed feature execution plan by aggregating data from existing project documents into a single plan.

Core Features & Use Cases

  • Compile scope, user flows, data model, and task mappings into docs/features/FXX_기능명_plan.md
  • Ensure traceability by referencing docs like user stories, IA structure, and architecture docs
  • Create or update docs/features/FXX_기능명_plan.md when new features are defined or requirements change

Quick Start

To generate a feature plan, run the feature-spec skill to compile inputs from docs and tasks into docs/features/FXX_기능명_plan.md.

Frequently Asked Questions about feature-spec

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

FAQPage Schema
How do I consolidate user stories and architecture docs into a single feature execution plan?▼

To consolidate feature plans, this skill aggregates data from docs/user_stories.json, docs/ia.md, docs/conceptual_model.json, docs/logical_architecture.md, and tasks/tasks.json into a single source-backed feature spec at docs/features/FXX_기능명_plan.md.

What is the best way to ensure traceability when planning frontend feature development?▼

Ensuring traceability during frontend feature planning requires referencing source documents like user stories, IA structure, and logical architecture docs directly within the generated feature execution plan, linking scope and task mappings back to their origins.

Do I need existing project documentation files to generate a feature spec?▼

Yes, generating a feature spec requires existing project documentation. The skill compiles inputs specifically from docs/user_stories.json, docs/ia.md, docs/conceptual_model.json, docs/logical_architecture.md, and tasks/tasks.json to produce the consolidated plan.

Can I update an existing feature plan when requirements change?▼

You can update an existing feature plan when requirements change. Running the skill creates or modifies docs/features/FXX_기능명_plan.md and updates tasks.json accordingly, ensuring the consolidated spec reflects the latest project data.

How does compiling a feature spec from multiple docs help align frontend design?▼

Compiling a feature spec from multiple docs aligns frontend design by aggregating scope, user flows, data models, and task mappings into one concise document, ensuring all design decisions trace back to the conceptual model and logical architecture.

Related Skills

Explore More Software Engineering Skills→
darsoohoodarsoohoo

documentation-criteria

Create documentation templates and criteria for PRD, ADR, Design Doc, UI Spec, and Work Plan.

Community
Advanced
ASTRA-TECHNOLOGY-COMPANY-LIMITEDASTRA-TECHNOLOGY-COMPANY-LIMITED

sprint-progress

Updates sprint progress trackers based on file modifications in specified directories.

Official
Intermediate
apply-theapply-the
1

speckit-checklist

Generate requirement checklists from user briefs with CHK traceability.

Official
Advanced
shin0720shin0720

auto-sync

Automate synchronization of SPEC files, CHANGELOG entries, and project documentation.

Community
Basic