From sd0x-dev-flow
Tracks request document status and progress using a knowledge base. Useful for querying request status, managing document references, and monitoring progress.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sd0x-dev-flow:request-trackingExploreThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Keywords: request document, request, progress tracking, status, acceptance criteria, tech spec
requests/ Request documents (scope + acceptance)
↓ references
planning/ Tech specs (implementation details)
↓ references
adr/ Decision records (rationale)
↓ references
architecture/ Architecture docs (system design)
docs/features/{feature}/
├── requests/ # Active request documents
│ └── archived/ # Completed
├── planning/ # Tech specs
├── adr/ # Decision records
└── architecture/ # Architecture docs
Format: YYYY-MM-DD-kebab-case-title.md
| Status | Description |
|---|---|
| Pending | Not started |
| In Dev | In progress |
| Approved | Spec confirmed |
| Priority | Timeline |
|---|---|
| P0 | Immediate |
| P1 | This week |
| P2 | This iteration |
## Request Status
| Request | Status | Priority | Updated |
|---------|--------|----------|---------|
| ... | ... | ... | ... |
references/template.md - Request document templatereferences/operations.md - Operations guideInput: How to write a request document?
Action: Explain template structure + reference references/template.md
Input: How to track progress for this request?
Action: Explain progress table / Phase breakdown approach
npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flowCreates, updates, scans, or batch-updates per-task request tickets for progress tracking. Supports flags like --status for scanning and --update-all for batch updates.
Analyzes feature requests, maintains PRDs, and decomposes into tracks with work breakdowns and execution order. For new feature planning, architecture changes, requirements analysis, or plan adjustments.
Manages PRD lifecycle: applies naming conventions, maintains directory structure, enforces status transitions, links PRDs to tasks, runs quality checks, and automates archiving.