npx claudepluginhub jmylchreest/aide --plugin aideThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.
Recommended model tier: smart (opus) - this skill requires careful reasoning
Structured planning interview to decompose work into independent stories before running a swarm.
plan swarm → Full interview workflow (recommended)
plan swarm --fast → Skip interview, state assumptions, decompose directly
Explore the codebase and existing context before asking questions.
mcp__plugin_aide_aide__decision_list and mcp__plugin_aide_aide__decision_getmcp__plugin_aide_aide__memory_search for relevant past contextDo NOT ask questions yet. Build understanding first.
Conduct 2-3 rounds of focused questions. Each round has 2-4 questions. Max 3 rounds total.
Round 1: Scope & Boundaries
Round 2: Dependencies & Risks
Round 3: Acceptance Criteria (if needed)
Use the AskUserQuestion tool for each round. Summarize what you've learned before asking the next round.
Fast mode (plan swarm --fast): Skip this phase. State your assumptions explicitly, then proceed directly to Phase 3.
Output a structured story list. Each story must be:
Story format:
## Stories
### 1. [Story Name]
- **Description**: What this story implements
- **Files**: List of files this story will create or modify
- **Acceptance Criteria**:
- [ ] Criterion 1
- [ ] Criterion 2
- **Risk**: low | medium | high
- **Notes**: Any special considerations
### 2. [Story Name]
...
Independence check: Verify that no two stories modify the same file. If they do, either:
./.aide/bin/aide decision set "swarm-plan" "<N> stories: <story-1>, <story-2>, ..." \
--details='<JSON object>' \
--rationale="<brief description of scope and approach>"
./.aide/bin/aide decision set "<topic>" "<decision>"
Binary location: The aide binary is at .aide/bin/aide. If it's on your $PATH, you can use aide directly.
/aide:swarm to execute the planNote on task materialization: The plan is stored as a decision, not as tasks. The /aide:swarm skill reads the plan and materializes tasks at execution time:
TaskCreate) with blockedBy dependency chaining for SDLC stages.task_create MCP tool) for all SDLC stages upfront, and story agents claim them.The stored swarm-plan decision should be a JSON object:
{
"stories": [
{
"name": "story-name",
"description": "What it does",
"files": ["src/foo.ts", "src/bar.ts"],
"acceptance": ["criterion 1", "criterion 2"],
"risk": "low",
"notes": ""
}
],
"shared_decisions": ["auth-strategy", "db-schema"],
"assumptions": ["Node 20+", "existing test framework"],
"created": "ISO timestamp"
}