plan-feature

name	plan-feature
description	Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
metadata	{"triggers":{"keywords":["plan feature","workflow"]}}

Plan Feature Skill

[!IMPORTANT] Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.

Instructions

When the user asks to perform this workflow, execute the following steps:

Feature Planning Workflow (PRD / What)

Goal: Produce a decision-complete PRD and implementation plan before code starts.

Steps

1. Load context:
   • Load baseline: docs/requirements-standards-baseline.md (PRD section).
   • BRD-lite brief, ticket, or user request.
   • Jira/GitHub/GitLab/ADO MCP ticket data when configured; otherwise local ticket text.
   • Existing specs, design references, and repo patterns.
   • common-product-requirements, quality-engineering-business-analysis, and matched framework skills.
2. Interview:
   • Ask only for business logic, scope, constraints, and acceptance criteria that cannot be inferred.
   • Confirm problem statement, assumptions, target users, JTBD/use cases, platforms, data, analytics, security, performance, rollout, and non-goals.
   • Confirm each requirement has owner, priority, and status.
   • Confirm success metrics and guardrails that must not regress.
   • Stop when requirements are actionable.
3. Draft PRD:
   • Save to docs/specs/prd-[slug].md when file writes are allowed.
   • Keep "what" separate from "how".
   • Add stable requirement IDs and AC IDs.
   • Use Given/When/Then AC when behavior can be misread.
   • Check user stories for specific persona, business value, INVEST, happy path, edge path, and negative path.
   • Link each requirement back to BRD-lite business objective.
   • Include risk categories, rollout/ops, decision log, analytics/telemetry, and changelog.
   • Mark unresolved items as blockers, not assumptions.
4. Create implementation plan:
   • Define components, contracts, data changes, migrations, risks, and verification.
   • Slice work into fresh-context tasks.
   • Identify whether design-solution is required before coding.
5. Route:
   • Architecture unclear -> design-solution.
   • Plan approved and build-ready -> implement-feature.

Output

Output Template

# Feature Plan: [Name]
## PRD
## Problem Statement
## Goals And Guardrails
## Personas / JTBD
## Use Cases
## Requirement Trace
## User Stories And ACs
## Decisions

| Decision   | Choice   | Reason   |
| ---------- | -------- | -------- |
| [decision] | [choice] | [reason] |
## Analytics / Telemetry
## Risks And Assumptions
## Rollout / Ops
## Implementation Plan
## Task Slices
## Verification Plan
## Next Workflow

design-solution | implement-feature
## Cost Report