goap-agent
GOAP Agent Skill
Goal-Oriented Action Planning for complex multi-step tasks with intelligent planning and multi-agent coordination.
Quick Reference
- Methodology - Core GOAP planning cycle and phases
- Execution Strategies - Parallel, Sequential, Swarm, Hybrid patterns
- Skills Reference - Available skills by category
- Agents Reference - Available task agents and capabilities
- Patterns - Common GOAP execution patterns
- Examples - Complete GOAP workflow examples
- ADR-022 - Architecture Decision Record
When to Use
- Complex multi-step tasks (5+ distinct steps)
- Cross-domain problems (storage, API, testing, documentation)
- Tasks requiring parallel/sequential execution
- Quality-critical work with validation checkpoints
- Large refactors or architectural changes
CRITICAL: Skills vs Task Agents
Skills (via Skill tool): Instruction sets that guide Claude directly
Agents (via Task tool): Autonomous sub-processes that execute tasks
Example:
- WRONG:
Task(subagent_type="code-quality", ...)→ ERROR! - CORRECT:
Skill(command="code-quality")→ SUCCESS
See skills.md for complete skills list and agents.md for agent capabilities.
Core Process
- ANALYZE → Understand goals, constraints, resources
- Check ADRs: Read relevant ADRs from
plans/adr/before planning
- Check ADRs: Read relevant ADRs from
- DECOMPOSE → Break into atomic tasks with dependencies
- STRATEGIZE → Choose execution pattern
- COORDINATE → Assign to specialized agents
- EXECUTE → Run with monitoring and quality gates
- SYNTHESIZE → Aggregate results and validate success
PR Monitoring Guardrail
- During EXECUTE/SYNTHESIZE for PR work, always verify
statusCheckRollupon the latest head SHA. - Treat an empty required-check rollup as a blocker and document it in
plans/STATUS/VALIDATION_LATEST.md. - Avoid adding plans-only follow-up commits until remediation checks are attached.
See methodology.md for detailed phase-by-phase guidance and patterns.md for common execution patterns.
ADR Integration Workflow
MANDATORY: Always check ADRs in plans/adr/ before creating execution plans:
Step 1: ADR Discovery
# List all ADRs to identify relevant ones
ls plans/adr/ADR-*.md
Step 2: Read Relevant ADRs
- Search for ADRs related to your task domain
- Note architectural decisions and constraints
- Check ADR status (Accepted/Implemented vs Deprecated)
Step 3: Incorporate into Planning
- Use ADR constraints when decomposing tasks
- Reference ADRs in execution plans
- Ensure compliance with architectural decisions
Step 4: Update Progress in plans/
- Create/update execution plan files in
plans/ - Document progress, blockers, and decisions
- Link to relevant ADRs in plan files
More from d-o-hub/rust-self-learning-memory
loop-agent
Execute workflow agents iteratively for refinement and progressive improvement until quality criteria are met. Use when tasks require repetitive refinement, multi-iteration improvements, progressive optimization, or feedback loops until convergence.
51web-search-researcher
Research topics using web search and content fetching to find accurate, current information. Use when you need modern information, official documentation, best practices, technical solutions, or comparisons beyond your training data.
46perplexity-researcher-reasoning-pro
Highest level of research and reasoning capabilities for complex decision-making with significant consequences, strategic planning, technical architecture decisions, multi-stakeholder problems, or high-complexity troubleshooting requiring expert-level judgment and sophisticated reasoning chains. Prioritizes actively maintained repositories and validates website sources for 2025 relevance.
44context-retrieval
Retrieve relevant episodic context from memory for informed decision-making. Use when you need past episodes, patterns, or solutions to similar tasks.
44rust-code-quality
Perform comprehensive Rust code quality reviews against best practices for async Rust, error handling, testing, and project structure
43codebase-analyzer
Analyze implementation details, trace data flow, explain technical workings, locate files, and consolidate codebases. Use when you need to understand HOW code works, find file locations, or assess technical debt.
40