File contents Request Tracking Skill
Trigger
Keywords: request document, request, progress tracking, status, acceptance criteria, tech spec
When NOT to Use
Create new request document (use /create-request)
Write tech spec (use /tech-spec)
Code development (use feature-dev)
Document Hierarchy
requests/ Request documents (scope + acceptance)
↓ references
planning/ Tech specs (implementation details)
↓ references
adr/ Decision records (rationale)
↓ references
architecture/ Architecture docs (system design)
File Location
docs/features/{feature}/
├── requests/ # Active request documents
│ └── archived/ # Completed
├── planning/ # Tech specs
├── adr/ # Decision records
└── architecture/ # Architecture docs
Naming Convention
Format : YYYY-MM-DD-kebab-case-title.md
Status & Priority
Status
Description
Pending
Not started
In Dev
In progress
Approved
Spec confirmed
Priority
Timeline
P0
Immediate
P1
This week
P2
This iteration
Output
## Request Status
| Request | Status | Priority | Updated |
|---------|--------|----------|---------|
| ... | ... | ... | ... |
Verification
Request document includes: background, requirements, acceptance criteria
File naming follows convention
Correctly linked to tech spec
References
references/template.md - Request document templatereferences/operations.md - Operations guide
Examples
Input: 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
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1 --- 2 name: sd0xdev-sd0x-dev-flow-request-tracking 3 description: Request Tracking Skill 4 --- 5 6 # Request Tracking Skill 7 8 ## Trigger 9 10 - Keywords: request document, request, progress tracking, status, acceptance criteria, tech spec 11 12 ## When NOT to Use 13 14 - Create new request document (use /create-request) 15 - Write tech spec (use /tech-spec) 16 - Code development (use feature-dev) 17 18 ## Document Hierarchy 19 20 ``` 21 requests/ Request documents (scope + acceptance) 22 ↓ references 23 planning/ Tech specs (implementation details) 24 ↓ references 25 adr/ Decision records (rationale) 26 ↓ references 27 architecture/ Architecture docs (system design) 28 ``` 29 30 ## File Location 31 32 ``` 33 docs/features/{feature}/ 34 ├── requests/ # Active request documents 35 │ └── archived/ # Completed 36 ├── planning/ # Tech specs 37 ├── adr/ # Decision records 38 └── architecture/ # Architecture docs 39 ``` 40 41 ## Naming Convention 42 43 **Format**: `YYYY-MM-DD-kebab-case-title.md` 44 45 ## Status & Priority 46 47 | Status | Description | 48 | -------- | ------------------ | 49 | Pending | Not started | 50 | In Dev | In progress | 51 | Approved | Spec confirmed | 52 53 | Priority | Timeline | 54 | -------- | -------------- | 55 | P0 | Immediate | 56 | P1 | This week | 57 | P2 | This iteration | 58 59 ## Output 60 61 ```markdown 62 ## Request Status 63 | Request | Status | Priority | Updated | 64 |---------|--------|----------|---------| 65 | ... | ... | ... | ... | 66 ``` 67 68 ## Verification 69 70 - Request document includes: background, requirements, acceptance criteria 71 - File naming follows convention 72 - Correctly linked to tech spec 73 74 ## References 75 76 - `references/template.md` - Request document template 77 - `references/operations.md` - Operations guide 78 79 ## Examples 80 81 ``` 82 Input: How to write a request document? 83 Action: Explain template structure + reference references/template.md 84 ``` 85 86 ``` 87 Input: How to track progress for this request? 88 Action: Explain progress table / Phase breakdown approach 89 ``` 90 91 --- 92 > Converted and distributed by [TomeVault](https://tomevault.io/claim/sd0xdev) — claim your Tome and manage your conversions. 93 <!-- tomevault:4.0:skill_md:2026-04-11 -->
commit ffc6be10e2
Frequently asked questions How do I install the Sd0xdev Sd0x Dev Flow Request Tracking skill? Run npx skillmds@latest add tomevault-io/sd0xdev-sd0x-dev-flow-request-tracking in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Sd0xdev Sd0x Dev Flow Request Tracking skill do? Request Tracking Skill It is listed under Coding & Dev Tools on SkillMD.
Is Sd0xdev Sd0x Dev Flow Request Tracking safe to use? This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Sd0xdev Sd0x Dev Flow Request Tracking? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Sd0xdev Sd0x Dev Flow Request Tracking free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Sd0xdev Sd0x Dev Flow Request Tracking? tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io