aidex-requestlisted

Use when the user relays an incoming stakeholder, client, or product request that should be captured as a written `.context/requests/` item before anyone acts on it — a feature ask, a requirement from a meeting, user feedback to formalize. Fires on "the client asked for X", "the stakeholder wants X", "capture this as a request", "log this requirement", "we got a request to add X". Not for: planning multi-step work (aidex-plan); recording a decision/ADR (aidex-decision); investigating how something works (aidex-research); documenting a settled reference (aidex-reference); deferring/parking an idea (aidex-backlog); ecosystem audits (aidex); project-state audits (aidex-audit).
yacb2/aidex · ★ 2 · AI & Automation · score 78

Install: claude install-skill yacb2/aidex

> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-request"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Request Capture an incoming stakeholder, client, or product request as a written item in `.context/requests/` before anyone acts on it. This skill is the single-purpose entry point for **request capture**; the formatting canon lives in the shared `aidex-conventions` reference package (not forked here). ## Workflow 1. Read the request conventions canon: `~/.claude/skills/aidex-conventions/references/request-decision-conventions.md` (Requests section; or `.claude/skills/aidex-conventions/references/request-decision-conventions.md` if a project-level copy exists). 2. Create a single dated file: `.context/requests/YYYY-MM-DD-<slug>.md` (slug kebab-case, date `YYYY-MM-DD`). 3. Front-matter per the canon — base lifecycle status (`open`/`doing`/`done`/`dropped`) plus `origin`, `origin_ref`, `priority`, `escalated_to`, `blocked_by`. 4. Body per the canon template: **Description**, **Context**, **Acceptance Criteria**, **Outcome**. A request is always a single file; if it needs depth it escalates to a plan or research. Write the artifact in English (canon §Language). ## Closing a request When a request reaches a terminal state, close it atomicall