Create a deferred features document capturing enhancements and ideas discovered during task execution
Create a deferred features document that captures enhancements, ideas, and descoped items discovered during task execution, organized for future planning.
The PM invokes this skill after completing a task or phase when deferred items have accumulated. It ensures that good ideas discovered during implementation are captured systematically rather than lost.
The PM provides these in natural language when invoking the skill:
| Parameter | Required | Description |
|---|---|---|
| Phase number | Yes | The phase number to scan for deferred items (e.g., p1, p2) |
| Task ID | Yes | The task identifier within the phase (e.g., t1.1, t3.10) |
| Feature name | Yes | A descriptive name for the document title (e.g., gate-skills, parallel-execution) |
/deferred p1 t1.2 gate-skills
/deferred Phase 2, task 2.3, feature name "session-management"
/deferred p3 t3.10 parallel-execution — we descoped a lot during this one, check the discovery logs carefully
When invoked, follow these steps in order:
CLAUDE.md for project context and directory conventions.worktickets/completed/ for finished ticketsworktickets/active/ for any in-progress ticketworktickets/draft/ for tickets that were drafted but not starteddocs/charter.md or as referenced in CLAUDE.md), review it to understand the original scope and intent for this task.Scan all gathered material for items in these categories:
Group the identified items into 5-6 thematic categories. Categories should be meaningful to the project, not generic. Examples of category types (adapt to actual content):
Each category should contain 3-5 items, targeting 20-25 enhancement ideas total across all categories.
For each item, assess two dimensions:
Present this as a matrix or table so the PM can quickly identify high-impact/low-effort wins versus long-term investments.
Organize the items into a recommended phased implementation plan:
docs/deferred-features/ directory exists in the project. If it does, follow the naming and formatting patterns already established there.docs/deferred-features/deferred_<phase>_<task>_<feature-name>.md with this structure:
If an OVERRIDES.md file exists in this skill's folder, read it after these instructions for project-specific customizations.