requestlisted
Install: claude install-skill yacb2/aidex
# 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 `conventions` reference package (not forked here).
## Workflow
1. Read the request conventions canon:
`${CLAUDE_PLUGIN_ROOT}/skills/conventions/references/request-decision-conventions.md`
(Requests section; or `.claude/skills/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 atomically (stamps `updated`,
sets the terminal status, archives per D-10) instead of hand-editing:
```bash
bash ${CLAUDE_PLUGIN_ROOT}/skills/conventions/scripts/close-dated-artifact.sh requests <slug> [--status done|dropped]
```
A request escalated to a plan sets `escalated_to: plan/<slug>` first, then closes
with `--stat