Request Tracking

Name: Request Tracking
Author: sd0xdev

ASecurity

Request tracking knowledge base. Covers request structure, status tracking, document references, progress management.

191 stars
0 votes
0 copies
1 view
Added February 7, 2026

development

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add sd0xdev/sd0x-dev-flow --skill request-tracking --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Request Tracking?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Request Tracking

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sd0xdev-request-tracking/badge)](https://www.skillsdirectory.com/skills/sd0xdev-request-tracking)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: request-tracking
description: Request tracking knowledge base. Covers request structure, status tracking, document references, progress management.
allowed-tools: Read, Grep, Glob
context: fork
agent: Explore
---

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