skills.rest
zazzcode
zazzcodeCOMMUNITY
Explore all skills by this author →
GitHub

feature-doc-builder

Create and evolve feature documents with purpose, current state, and milestones.

3|1|Updated Feb 19, 2026
Search Tags:#planning#milestones#product-management#stakeholders#feature-definition#feature-document
One-click install
npx skills add https://github.com/zazzcode/zazz-skills --skill feature-doc-builder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-doc-builder
Source: https://github.com/zazzcode/zazz-skills/tree/main/.agents/skills/feature-doc-builder
Command: npx skills add https://github.com/zazzcode/zazz-skills --skill feature-doc-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and maintaining durable feature documents that capture why a capability exists, the current system state, and how it should evolve over time.

Core Features & Use Cases

  • Draft, refine, and evolve long-lived feature documents to align product, design, and engineering teams.
  • Capture feature purpose, current live behavior, gaps, and milestone-based evolution to guide later deliverables.
  • Provide handoff inputs and templates for proposal, spec, and plan artifacts while preserving long-term context.

Quick Start

Initiate a dialogue to draft or update a feature document that captures purpose, current state, and milestone roadmap.

Frequently Asked Questions about feature-doc-builder

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

FAQPage Schema
How do I create a feature document that captures purpose and current state?▼

The best way to structure milestone planning is by capturing feature purpose, current live behavior, and gaps within a durable feature document, using dialogue-driven revision to map milestone-based evolution and stakeholder handoffs.

What is a durable feature document and when do I need one?▼

A durable feature document is a long-lived artifact that captures why a capability exists, current system state, and evolution plans, needed when aligning product, design, and engineering teams across evolving feature milestones.

How do I align stakeholders and engineering teams during feature definition?▼

Align stakeholders by drafting and refining long-lived feature documents that capture feature purpose, current gaps, and milestone-based evolution, preserving long-term context through dialogue-driven revision.

Does feature definition work for planning handoffs to spec and plan artifacts?▼

Feature definition supports planning handoffs by providing structured inputs and templates for proposal, spec, and plan artifacts while preserving the long-term context of the feature document.

Can I update an existing feature document as milestones evolve over time?▼

You can update an existing feature document through dialogue-driven revision, allowing product owners and stakeholders to continuously refine purpose, current state, and milestone roadmaps as the feature evolves over time.

Related Skills

Explore More Product & Management Skills→
LuigiAPCPereiraLuigiAPCPereira
1

brainstorming

Guide initial concepts into detailed technical designs through structured questioning.

Community
Intermediate
tylerwindtylerwind
47

writing-plans

Generate task-by-task implementation plans from feature specs.

Community
Advanced
LeKayLeKay

milestone-review

Assess feature completeness, quality metrics, and risk for milestone checkpoints.

Community
Intermediate
safzanpiranisafzanpirani
1

prd-to-issues

Convert a Product Requirements Document into individual markdown issue files.

Community
Intermediate