Decisions
User Tasks
FR-028: Feature Request Workflow Automation
Summary
Automate the feature request lifecycle — creation, status transitions, and dashboard updates.
Problem / Motivation
Manually creating feature requests from the template, moving files between folders, and updating the overview dashboard is tedious and error-prone.
Proposed Solution
Python scripts (or Claude Code automation) that handle feature lifecycle operations: create, transition, and generate overview updates.
Open Questions
No open questions.
Phase Overview
| Phase | Description | Status |
|---|
| Phase 1 | CLI Tools | — |
| Phase 2 | Claude Integration | — |
| Phase 3 | Advanced | — |
Goal: Basic command-line scripts for feature lifecycle management.
| File / Feature | Details | Owner | Status |
|---|
| Create script | Create a new feature request from template (auto-increment ID) | opus | — |
| Transition script | Move a feature between lifecycle stages | opus | — |
| Overview script | Regenerate the feature overview dashboard | opus | — |
Phase 2: Claude Integration —
Goal: Enable Claude Code to invoke lifecycle scripts as part of autonomous workflows.
| File / Feature | Details | Owner | Status |
|---|
| Script invocation | Claude Code can invoke these scripts | opus | — |
| Natural language commands | ”create feature request for X” | opus | — |
| Auto-update overview | After any feature change | opus | — |
sync-overview hook | PostToolUse: regenerate feature overview after FR changes | opus | — |
Phase 3: Advanced —
Goal: Dependency tracking and automated prioritization.
| File / Feature | Details | Owner | Status |
|---|
| Feature dependency tracking | Track which FRs depend on others | opus | — |
| Effort estimation | Estimate effort for each FR | opus | — |
| Automated prioritization | Suggestions based on dependencies | opus | — |
Acceptance Criteria:
Notes:
- Start simple — even a bash script is fine for Phase 1.
- This is a “meta-feature”: it improves the system’s ability to manage itself.
Prerequisites / Gap Analysis
Requirements
| Requirement | Description |
|---|
| REQ-1 | FR-009 (Python Project Scaffold) for Python-based scripts |
Current State
| Component | Status | Details |
|---|
| Feature template | done | _templates/feature-request.md exists |
| Feature lifecycle folders | done | inbox/new/planned/in-progress/done exist |
| Automation scripts | — | None exist |
Gap (What’s missing?)
| Gap | Effort | Blocker? |
|---|
| CLI scripts for lifecycle operations | Med | No |
Test
Manual tests
| Test | Expected | Actual | Last |
|---|
| Create new FR via script | FR file created with correct ID and template | pending | - |
| Transition FR to next stage | File moved, frontmatter updated | pending | - |
| Regenerate overview | Overview matches actual FR files | pending | - |
AI-verified tests
| Scenario | Expected behavior | Verification method |
|---|
| … | … | … |
E2E tests
Integration tests
Unit tests
| Component | Tests | Coverage |
|---|
| … | … | … |
History
| Date | Event | Details |
|---|
| 2026-02-26 | Created | As part of Phase 1 foundation |
| 2026-02-27 | Renumbered | From FR-020 to FR-028 |
| 2026-02-28 | Reformatted | Aligned to feature-request template |
References
- FR-009 (Python Project Scaffold) — prerequisite for Python scripts
- FR-027 (Feature Overview Sync Check) — related overview automation