Feature Planning
Purpose
Plan a feature: define its scope within the architecture, its design decisions, tasks, and tests, so it can be implemented and verified without scope creep. Produces a feature work item in ../../work-items/features/.
When to Use
- Request classified as feature (or a feature sub-part of a larger plan).
- When adding capability to an existing or planned architecture.
- Not for defect fixes (
bug-investigation) or behavior-preserving cleanup (refactor-planning).
Inputs
- Requirement baseline + success criteria.
- Architecture + repository layout.
- Existing patterns (from
existing-project-audit) for consistency.
Discovery Questions
- What exactly is in scope, and what is explicitly out?
- Which applications/modules does it touch?
- What are the acceptance criteria from the user's perspective?
- What tests prove it works (levels/tools)?
- Any security-sensitive surface (auth, payments, PII)?
Responsibilities
- Define the feature's scope and boundaries (in/out).
- Fit it to existing architecture and patterns.
- Produce tasks (via
task-planning) with acceptance criteria written as Gherkin scenarios (testing/gherkin-specifications, ../../system/GHERKIN_RULES.md) — including the required cases, one scenario each.
- Attach a testing plan (
testing-strategy) and security requirements (security-review) where relevant.
- Record the feature work item and its status.
Required Workflow
- Read requirements + architecture, and the existing scenarios for the area.
- Lock scope (in/out) and acceptance criteria as Gherkin scenarios — happy, invalid, error, authorization denial, and the relevant edge cases — approved at Gate 2 before design (
../../system/GHERKIN_RULES.md). The approved scenarios are the scope.
- Identify affected apps/modules and contracts.
- Generate tasks (delegate mechanics to
task-planning).
- Attach tests + security requirements.
- Record in
../../work-items/features/.
- On a tracked project, hand to
project-management to assign IDs, a phase, and a week — and to flag SCOPE CHANGE if the feature wasn't in the approved plan.
Decision Rules
- Match existing conventions rather than introducing new patterns without cause.
- Build on the existing technology when it can deliver the feature correctly; a new framework, library, or upgrade needs a recorded trigger (
../../system/TECHNOLOGY_GOVERNANCE_RULES.md).
- Security-sensitive features get integration/E2E tests, not just units.
- New work discovered mid-plan → propose a separate work item, don't absorb it.
Rules
- Stay within the feature's stated scope.
- Preserve unrelated behavior.
- Acceptance criteria are observable and testable.
Anti-Patterns
- Scope creep ("while I'm here…").
- Introducing a new stack/pattern for one feature.
- Shipping without acceptance criteria or tests.
Validation Checklist
Definition of Done
A recorded feature work item with locked scope, acceptance criteria, tasks, a testing plan, and any security requirements — ready for implementation under the gates.
Related Skills
task-planning, architecture-design, testing-strategy, security-review, code-review, project-orchestrator, project-management.
Related Knowledge
../../knowledge/ (domain rules, patterns).
Related References
../../references/<domain-topic>/ when the feature domain needs grounding.
Context Loading Guidance
- Requires: requirements, architecture, affected-area patterns.
- Does not require: unrelated modules, the full reference tree, other planning skills' bodies.
- May load:
task-planning, testing-strategy, security-review.
- Stop when: the feature work item is recorded.
Token Efficiency Guidance
Load only the affected modules' context. Reuse task-planning for mechanics rather than restating them. Keep the work item concise.
1---2name: feature-planning3description: Use to plan a feature work item — scoping new capability within existing (or planned) architecture, defining its phases, tasks, tests, and acceptance criteria without expanding scope. Delegates general phase/task mechanics to task-planning.4metadata:5 source: https://skillmd.com/skills/ahtishamshahzad/feature-planning6---78# Feature Planning910## Purpose1112Plan a feature: define its scope within the architecture, its design decisions, tasks, and tests, so it can be implemented and verified without scope creep. Produces a feature work item in `../../work-items/features/`.1314## When to Use1516- Request classified as **feature** (or a feature sub-part of a larger plan).17- When adding capability to an existing or planned architecture.18- **Not** for defect fixes (`bug-investigation`) or behavior-preserving cleanup (`refactor-planning`).1920## Inputs2122- Requirement baseline + success criteria.23- Architecture + repository layout.24- Existing patterns (from `existing-project-audit`) for consistency.2526## Discovery Questions2728- What exactly is in scope, and what is explicitly out?29- Which applications/modules does it touch?30- What are the acceptance criteria from the user's perspective?31- What tests prove it works (levels/tools)?32- Any security-sensitive surface (auth, payments, PII)?3334## Responsibilities3536- Define the feature's **scope and boundaries** (in/out).37- Fit it to existing **architecture and patterns**.38- Produce **tasks** (via `task-planning`) with acceptance criteria written as Gherkin scenarios (`testing/gherkin-specifications`, `../../system/GHERKIN_RULES.md`) — including the required cases, one scenario each.39- Attach a **testing plan** (`testing-strategy`) and **security requirements** (`security-review`) where relevant.40- Record the feature work item and its status.4142## Required Workflow43441. Read requirements + architecture, and the existing scenarios for the area.452. Lock scope (in/out) and acceptance criteria **as Gherkin scenarios** — happy, invalid, error, authorization denial, and the relevant edge cases — approved at Gate 2 before design (`../../system/GHERKIN_RULES.md`). The approved scenarios *are* the scope.463. Identify affected apps/modules and contracts.474. Generate tasks (delegate mechanics to `task-planning`).485. Attach tests + security requirements.496. Record in `../../work-items/features/`.507. On a tracked project, hand to `project-management` to assign IDs, a phase, and a week — and to flag `SCOPE CHANGE` if the feature wasn't in the approved plan.5152## Decision Rules5354- Match existing conventions rather than introducing new patterns without cause.55- Build on the existing technology when it can deliver the feature correctly; a new framework, library, or upgrade needs a recorded trigger (`../../system/TECHNOLOGY_GOVERNANCE_RULES.md`).56- Security-sensitive features get integration/E2E tests, not just units.57- New work discovered mid-plan → propose a separate work item, don't absorb it.5859## Rules6061- Stay within the feature's stated scope.62- Preserve unrelated behavior.63- Acceptance criteria are observable and testable.6465## Anti-Patterns6667- Scope creep ("while I'm here…").68- Introducing a new stack/pattern for one feature.69- Shipping without acceptance criteria or tests.7071## Validation Checklist7273- [ ] Scope (in/out) explicit.74- [ ] Affected apps/modules identified.75- [ ] Acceptance criteria observable/testable.76- [ ] Tasks generated with criteria.77- [ ] Testing plan attached.78- [ ] Security requirements attached where relevant.7980## Definition of Done8182A recorded feature work item with locked scope, acceptance criteria, tasks, a testing plan, and any security requirements — ready for implementation under the gates.8384## Related Skills8586`task-planning`, `architecture-design`, `testing-strategy`, `security-review`, `code-review`, `project-orchestrator`, `project-management`.8788## Related Knowledge8990`../../knowledge/` (domain rules, patterns).9192## Related References9394`../../references/<domain-topic>/` when the feature domain needs grounding.9596## Context Loading Guidance9798- **Requires:** requirements, architecture, affected-area patterns.99- **Does not require:** unrelated modules, the full reference tree, other planning skills' bodies.100- **May load:** `task-planning`, `testing-strategy`, `security-review`.101- **Stop when:** the feature work item is recorded.102103## Token Efficiency Guidance104105Load only the affected modules' context. Reuse `task-planning` for mechanics rather than restating them. Keep the work item concise.