skills/request-tracking/SKILL.md
Request tracking knowledge base. Use when: querying request status, managing document references, tracking progress. Not for: creating requests (use create-request), tech specs (use tech-spec). Output: status report + progress tracking.
npx skillsauth add sd0xdev/sd0x-dev-flow request-trackingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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
documentation
Rewrite the previous reply in Traditional Chinese
development
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
development
Verification loop — lint -> typecheck -> unit -> integration -> e2e
development
Research current code state then update corresponding docs, ensuring docs stay in sync with code.