agentsclimarketplace
Sign in

Aidex request

Skill yacb2/aidex/skills/aidex-request

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).From its SKILL.md

Install
npx -y skills add yacb2/aidex --skill aidex-request

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 3 commands, including `printenv AIDEX_TRIGGER_EVAL_MARKER` and 2 more.

SKILL.md

3.7 KB, 745 tokens by cl100k_base, as published. Nobody here has run it

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 atomically (stamps updated, sets the terminal status, archives per D-10) instead of hand-editing:

bash ~/.claude/skills/aidex-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 --status done.

Self-check (mandatory close step)

Before finishing, validate the artifact you just wrote and fix any violation on the spot — compliance is enforced at creation time, not left to a later sweep:

python3 ~/.claude/skills/aidex-conventions/scripts/validate.py --type requests

If the project carries a ratchet baseline (.context/.validate-baseline.json), a non-zero exit means you introduced a NEW violation — fix it before closing.

Boundaries

The user wants to…Route to
Plan multi-step / multi-phase implementation workaidex-plan
Record a decision / ADRaidex-decision
Investigate / research how something worksaidex-research
Document a settled system referenceaidex-reference
Capture a received/sent communication (email/WhatsApp/call)aidex-comm
Defer / park / shelve an idea for lateraidex-backlog
Audit the Claude Code ecosystemaidex
Audit project state (UX/security/perf/a11y)aidex-audit

Related

  • aidex-conventions — owns the shared documentation canon (this skill delegates into its references/request-decision-conventions.md).

What ships with it: 2 files

5.5 KB alongside SKILL.md

evals/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.