Request Tracking
Productivityrequest-trackingRequest Tracking is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Request tracking knowledge base. Covers request structure, status tracking, document references, progress management.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/request-tracking/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/request-tracking, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 |
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 template.md
Input: How to track progress for this request?
Action: Explain progress table / Phase breakdown approach