feature-plan

Decomposes a product-plan grouping into per-feature specs and scout-builder dispatch sequences.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/hontauadrian/sfx-app-empty-test --skill feature-plan-hontauadrian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-plan
Source: https://github.com/hontauadrian/sfx-app-empty-test/tree/main/.claude/skills/feature-plan
Command: npx skills add https://github.com/hontauadrian/sfx-app-empty-test --skill feature-plan-hontauadrian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a lead or coordinator receives a chunk of a product plan, they need a repeatable way to break that grouping into concrete per-feature specs and ordered agent dispatches without re-doing the product plan or writing vague scout prompts. ## Core Features & Use Cases - Feature decomposition: Splits an assigned chunk (lead) or the full §3 feature list (coordinator in direct-builder mode) into vertical-slice features with outcomes, target files, dependencies, runtime acceptance, and guard contracts. - Scout dispatch planning: Drafts concrete scout prompts with specific files to read, spec templates, auth-preservation notes, and nested-resource @ResourceCaptures carve-outs. - Dispatch sequencing: Plans scout/builder ordering based on MAX AGENTS, from parallel overlap to strictly sequential single-agent execution. - Use Case: A lead assigned the "teams" chunk of a product plan uses this skill to produce three feature specs, three scout prompts, and a dispatch order before running sd create and ov sling. ## Quick Start Ask the agent to use the feature-plan skill to break your assigned product-plan chunk into per-feature specs and a scout-builder dispatch plan.

Frequently Asked Questions about feature-plan

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

FAQPage Schema
How do I break a product plan into per-feature specs?▼

Identify your grouping (one chunk for a lead, the full §3 list for a coordinator in direct-builder mode), then define each feature as a vertical slice with an outcome, target files, dependencies, runtime acceptance, and a guard contract. Dispatch a scout per feature to write the actual spec file.

What should a scout prompt include when dispatching feature specs?▼

A scout prompt must name the product-plan spec path, the exact feature to spec, concrete files to read first, the spec template to produce, and the output path. It must also include auth-preservation and nested-resource @ResourceCaptures carve-out notes where applicable.

How does MAX AGENTS affect the scout and builder dispatch order?▼

With MAX AGENTS ≥ 3, scouts and builders overlap in parallel. With 2, work is strictly sequential: scout, then its builder, then the next scout. With 1, the lead implements each feature directly without sub-spawns.

When should feature specs preserve the existing auth stack?▼

Unless the product plan explicitly requests auth replacement, all feature specs and scout prompts must keep the existing scaffold auth provider untouched. Do not add email/password auth, /login, /register, or local JWT cookies, and do not remove the existing proxy or OAuth configuration.

Why do builders get blocked on nested resource routes?▼

When a feature adds child routes under an existing parent path, a blanket "do not modify" clause on the parent module blocks a required additive @ResourceCaptures tuple on the parent CREATE handler. Scout prompts must explicitly carve out this metadata-only exception.