How do I install the Request Tracking skill?

Run npx skillmds@latest add sd0xdev/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.

Is 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 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 Request Tracking free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Request Tracking?

sd0xdev (@sd0xdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Request Tracking by sd0xdev — Agent Skill

Name: Request Tracking
Author: sd0xdev

Request Tracking

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.

sd0xdev Updated Sep 17, 2026

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 template
references/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

---name: request-trackingdescription: 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.---# 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) ↓ referencesplanning/ Tech specs (implementation details) ↓ referencesadr/ Decision records (rationale) ↓ referencesarchitecture/ 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```markdown## 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 template- `references/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```

Frequently asked questions