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.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

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

Feature Planning Workflow (PRD / What)

Goal: Produce a PM-owned decision-complete PRD, delivery plan, and IT Department handoff before code starts.

Steps

1. Load context:
   • Load baseline PRD section and search docs/brd/ for the matching [slug]; if multiple candidates exist and intent is unclear, ask the user to choose/input the target slug.
   • Load BRD-lite, ticket text, existing specs, repo patterns, common-product-requirements, common-operator-profile, quality-engineering-business-analysis, and matched framework skills.
   • Carry forward operator_profile, BRD objective IDs, SMART metric, scope fence, assumptions, glossary, risks, and delivery context.
2. Interview:
   • Draft a provisional PRD direction from current context before asking.
   • Ask only for business logic, scope, constraints, and acceptance criteria that cannot be inferred.