request-tracking

name

request-tracking

description

Route request-tracking using exact migration registry [{"unit":"request-tracking/default","routing":{"negative_boundaries":["Create or update a date-prefixed execution request ticket.","Scan only incomplete requests and show the operational work queue.","Verify one request acceptance criteria and mark its completion status."],"positive_triggers":["Build a read-only cross-feature request portfolio report with status, priority, age, blockers, and parse errors.","Show request health trends and broken dependency links without editing any tickets.","Summarize all active and terminal request metadata for planning governance."]}}].

Request Portfolio Tracking

Build a read-only, cross-feature portfolio report from date-prefixed request tickets. Summarize status, priority, age, acceptance progress, dependencies, blockers, terminal history, and parse errors for planning governance.

Do not create or edit request tickets, verify acceptance criteria, write closure state, update progress, or mutate Git. Evidence refs remain unchanged. An operational queue limited to incomplete tickets belongs to core create-request; this workflow covers portfolio health across active and terminal records.

1. Discover the portfolio

Inspect contained regular Markdown files directly under docs/features/{feature}/requests/ and its archived/ child. Reject absolute paths, traversal, symlinked ancestors/directories/files, nested request directories, and non-Markdown files. Count active-directory and archived-directory files separately; never infer archived status solely from location.

Accept an optional feature filter, status filter, date window, or explicit request set. Otherwise include every feature. Report unreadable or malformed files as per-file errors and continue with unrelated valid tickets.

2. Parse the request contract

Read the portfolio report contract.

For the metadata region before the first level-two heading, prefer canonical blockquote fields and fall back to the first fifteen lines of a legacy metadata table. Parse title, created date, implementation base, status, priority, dependencies, supersession links, and technical-spec link. Extract the filename date only when is absent.