parallel-setup
One-time setup of parallel/ directory for multi-agent development
What this skill does
# parallel-setup
**Category**: Parallel Development
## Usage
```bash
/parallel-setup [--tech django|typescript|go]
```
## Arguments
- `--tech`: Optional - Technology stack hint for future decompositions (default: auto-detect)
## Purpose
**One-time** initialization of the `parallel/` directory at project root for parallel multi-agent development. This creates the infrastructure for organizing decomposed tasks by Tech Spec.
> Run this once per project. Then use `/parallel-decompose` for each Tech Spec.
## Execution Instructions for Claude Code
When this command is run, Claude Code should:
### 1. Create Directory Structure
```bash
mkdir -p parallel
```
Creates:
```
parallel/
├── README.md # Explains parallel development workflow
└── .gitignore # What to track vs ignore
```
### 2. Create README.md
Create `parallel/README.md`:
```markdown
# Parallel Development Artifacts
This directory contains artifacts for parallel multi-agent development.
## Structure
Each Tech Spec decomposition creates a subdirectory:
```
parallel/
├── TS-0042-inventory-system/ # Keyed by Tech Spec ID
│ ├── manifest.json # Regeneration metadata
│ ├── context.md # Shared project context
│ ├── tasks/ # Task specifications
│ ├── contracts/ # Shared types & API schema
│ ├── prompts/ # Agent launch prompts
│ ├── scripts/ # Launch & monitor scripts
│ ├── architecture.md # System design
│ └── task-graph.md # Dependency visualization
└── ...
```
## Commands
- `/parallel-decompose <prd> --tech-spec <ts-file>` - Decompose PRD into tasks
- `/parallel-integrate --parallel-dir <dir>` - Verify integration
## Regeneration
Each subdirectory contains a `manifest.json` with metadata to regenerate artifacts:
```bash
# Re-run decomposition with same args
/parallel-decompose docs/prd.md --tech-spec tech-specs/approved/TS-XXXX.md
```
```
### 3. Create .gitignore
Create `parallel/.gitignore`:
```gitignore
# Generated prompts and scripts (regenerate with /parallel-decompose)
*/prompts/
*/scripts/
# Integration reports
*/integration-report.md
# Keep tracked:
# - manifest.json (regeneration metadata)
# - context.md (shared context)
# - tasks/ (task specifications)
# - contracts/ (shared types & API)
# - architecture.md (system design)
# - task-graph.md (dependencies)
```
### 4. Update CLAUDE.md (if exists)
If `CLAUDE.md` exists at project root, add a section:
```markdown
## Parallel Development
This project uses parallel multi-agent development. Artifacts are in `parallel/`.
- Each Tech Spec decomposition creates `parallel/TS-XXXX-{slug}/`
- Task files use compact YAML format for token efficiency
- Contracts are shared via `contracts/` subdirectory
- Run `/parallel-decompose --help` for usage
```
### 5. Report Results
Output summary:
```
Created parallel/ directory structure
parallel/
├── README.md # Workflow documentation
└── .gitignore # Track config
Next steps:
1. Create a Tech Spec: /create-tech-spec <title>
2. Decompose PRD: /parallel-decompose <prd> --tech-spec <ts-file>
```
## Example
```bash
# Initialize parallel development
/parallel-setup
# With technology hint
/parallel-setup --tech django
```
## Notes
- This command is idempotent - safe to run multiple times
- Existing files are NOT overwritten
- Creates foundation for `/parallel-decompose` command
- Each decomposition creates its own subdirectory (e.g., `parallel/TS-0042-slug/`)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.