feature-request

Draft requirements and design documents from new feature requests.

18|Updated Feb 14, 2020

Search Tags:#planning #specification #requirements #adr #handoff #feature request #epic

Ready to run

npx skills add https://github.com/subroh0508/colormaster --skill feature-request-subroh0508

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-request
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/feature-request
Command: npx skills add https://github.com/subroh0508/colormaster --skill feature-request-subroh0508

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns raw feature requests into structured requirements and design artifacts without forcing the user to do the documentation work manually.

Core Features & Use Cases

Requirements drafting: Converts a feature idea into a clear REQ document with scope, acceptance criteria, and traceability.
Basic and detailed design: Produces system-level and module-level specifications when the change needs more than a simple note.
Plan or Epic routing: Chooses the right follow-up workflow for single-PR or multi-PR work and hands off cleanly to the next skill.
Use case: A product owner asks for a new onboarding flow, and the Skill writes the requirements, drafts the designs, and triggers the right planning path.

Quick Start

Use the feature-request skill to turn this new product idea into a requirement, specification, and planning handoff.

Frequently Asked Questions about feature-request

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

FAQPage Schema

How do I turn a feature request into a requirements document and specification?▼

To turn a feature request into a requirements document and specification, provide the raw idea to generate a clear REQ document with scope, acceptance criteria, system-level basic SPEC, and module-level detail SPEC automatically.

What is the best way to plan a multi-PR epic from a product change request?▼

Planning a multi-PR epic from a product change request involves routing the drafted requirements and design documents to an epic-author workflow, ensuring clean handoff for complex feature scopes.

Can I capture architecture decision records when drafting design specifications?▼

Yes, you can capture architecture decision records (ADR) when drafting design specifications, integrating key technical decisions directly within the generated documentation for future traceability.

Does the feature planning workflow output code or only documentation?▼

The feature planning workflow outputs documentation only, enforcing code-free specifications, requirements, and ADRs to separate design artifacts from implementation entirely.

When do I need detailed specifications versus a basic spec for new features?▼

You need detailed specifications versus a basic spec for new features when the product change requires module-level design beyond a simple note, triggering system-level and module-level specification drafting.

How does single-PR scope differ from multi-PR epic triage in requirements planning?▼

Single-PR scope differs from multi-PR epic triage in requirements planning by routing the generated documentation to a plan-author workflow for simple changes, while multi-PR scope triggers an epic-author workflow.