beads-converter
CommandConvert plans to Beads - works with /beads-loop, /beads-swarm, or RalphTUI
Generate DEVGUIDE.md architectural documentation using LSP (project)
> /plugin marketplace add GantisStorm/essentials-claude-code> /plugin install essentials@essentials-claude-code
allowed-tools: Task, Glob, Read argument-hint: "<dir1> [dir2] ... [dirN]" description: Generate DEVGUIDE.md architectural documentation using LSP (project) context: fork model: opus
Generate hierarchical architectural documentation (DEVGUIDE.md) using Claude Code's built-in LSP tools. Supports multiple directories with parallel agent execution.
Directory paths to document (one agent per directory):
Parse `$ARGUMENTS` to extract directory list:
Check if `.claude/rules` directory exists at project root:
Use Glob(".claude/rules/*.md") to find rules files.
If rules exist:
- Read each rules file to understand frontmatter paths
- Pass relevant rules info to agents
If no rules exist:
- Note this for agents to create rules files when missingFor each directory:
For EACH directory, launch background agent:
Generate DEVGUIDE: <directory-path> Output: <determined path> Rules: <exists/not found>
**REQUIRED Task tool parameters:**
subagent_type: "essentials:document-creator-default" run_in_background: true prompt: "Generate DEVGUIDE: <dir>\nOutput: <path>\nRules: <status>"
**Launch ALL agents in a single message for parallel execution.** Output a status message like "Generating N DEVGUIDE files..." and **end your turn**. The system wakes you when agents finish.
## DEVGUIDE Documentation Created (LSP) | Directory | Output | Status | |-----------|--------|--------| | [dir1] | [output path] | CREATED | | [dir2] | [output path] | CREATED | Rules Status: [Found N rules / No rules folder found] Next Steps: 1. Review generated documentation 2. Commit the DEVGUIDE files 3. [If no rules] Agent created .claude/rules/ file automatically
| Scenario | Action | |----------|--------| | Path not found | Report error, continue with other paths | | Path is file not directory | Report error, continue with other paths | | Empty directory | Generate minimal guide | | Agent fails | Report error, suggest retry |
/document-creator /document-creator src/services/ /document-creator src/services src/components src/lib /document-creator backend/src frontend/src
Loops, swarms, and teams powered by Claude Code's built-in Task System. Loop, swarm, and team are three execution modes. Loop runs sequentially. Swarm runs parallel subagents. Team spawns full Claude Code instances with shared contracts via Agent Teams.
Convert plans to Beads - works with /beads-loop, /beads-swarm, or RalphTUI
Execute beads with parallel agent swarm (dependency-aware)
Deep bug investigation with architectural fix plan generation - works with any executor (loop or swarm)
One-time setup after installing ARIS as a Claude Code plugin — registers the Codex reviewer MCP server from the plugin directory…
Autonomous iteration loop: modify, verify, keep/discard against any metric
name: sc:agent description: SC Agent — session controller that orchestrates investigation, implementation, and review category:…