Skip to content
Back to skills

Request Tracking

ASecurity

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.

  • 192 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 4, 2026
ai-agents

Security analysis

A100/100

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

Scanned September 4, 2026

npx -y skills add sd0xdev/sd0x-harness --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-sd0x-harness/badge)](https://www.skillsdirectory.com/skills/sd0xdev-request-tracking-sd0x-harness)

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. 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."
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 |

## 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
```

Files in this skill

  • SKILL.md2.3 KB
  • references/operations.md1.8 KB
  • references/template.md1.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.