agentleFS
Sign inStart free
yacb2yacb2/aidex/skills/request/SKILL.md

request

Skill2 starsChanged 33 days agoMITView on GitHub

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:aidex); project-state audits (/aidex:audit).

18 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the request conventions canon: ${CLAUDE_PLUGIN_ROOT}/skills/conventions/references/request-decision-conventions.md (Requests section.

    line 17
  2. Very specific:

    Create a single dated file: .context/requests/YYYY-MM-DD-<slug>.md (slug kebab-case, date YYYY-MM-DD).

    line 21
  3. Very specific:

    When a request reaches a terminal state, close it atomically (stamps updated, sets the terminal status, archives per D-10) instead of …

    line 33
  4. Very specific:

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

    line 51

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 ${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 --status done.

Self-check

Validate the artifact you just wrote and fix any violation before closing:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/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 workplan
Record a decision / ADRdecision
Investigate / research how something worksresearch
Document a settled system referencereference
Capture a received/sent communication (email/WhatsApp/call)comm
Defer / park / shelve an idea for laterbacklog
Audit the Claude Code ecosystemaidex
Audit project state (UX/security/perf/a11y)audit

Related

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free