request-tracking

Automate request tracking documentation with templates and lifecycle stages.

187|24|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill request-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-tracking
Source: https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/request-tracking
Command: npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill request-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill centralizes and standardizes the documentation workflow for requests, reducing ambiguity and miscommunication across teams.

Core Features & Use Cases

  • Structured request documents with backgrounds, requirements, acceptance criteria, and references to planning artifacts.
  • A clear lifecycle model (Pending, In Dev, Approved) with archival of completed requests.
  • Templates and references to ensure consistent formatting and traceability across projects.

Quick Start

Create a new request document using the standard template, link it to the tech spec and ADR, and move it to the appropriate lifecycle stage as work progresses.

Frequently Asked Questions about request-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize request tracking documentation across multiple projects?

You can standardize request tracking by applying enforced naming conventions, using structured templates for backgrounds and requirements, and linking requests directly to planning artifacts like tech specs and ADRs.

How do I link active requests to tech specs and ADRs in my workflow?

You can link active requests to tech specs and ADRs by using templated references within a defined documentation hierarchy, ensuring traceability between the request background, acceptance criteria, and architecture decisions.

What is the best way to manage the lifecycle of a technical request document?

The best way to manage a technical request lifecycle is to move documents through Pending, In Dev, and Approved stages, archiving completed requests to maintain an uncluttered and traceable project history.

Can I use structured templates for architecture references and tech specs?

Yes, you can use structured templates to standardize architecture references and tech specs, ensuring consistent formatting for backgrounds, requirements, and acceptance criteria across all active project requests.

Why does centralizing request documentation reduce team miscommunication?

Centralizing request documentation reduces miscommunication by enforcing consistent formatting and establishing a clear lifecycle model, which eliminates ambiguity and ensures all teams reference the same standardized tech specs and ADRs.