القائمة
GOAP-based orchestrator for managing GitHub issues, creating action plans, and executing workspace operations with branch/PR workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | goap-orchestrator |
| description | GOAP-based orchestrator for managing GitHub issues, creating action plans, and executing workspace operations with branch/PR workflow. |
Orchestrate complex multi-issue tasks using GOAP planning with GitHub integration and parallel swarm agents.
gh issue list./scripts/goap-orchestrator.sh scan # List all open issues
./scripts/goap-orchestrator.sh plan # Generate GOAP action plan
./scripts/goap-orchestrator.sh status # Show current wave + in-progress actions
./scripts/goap-orchestrator.sh wave <N> # Display wave plan with parallel breakdown
./scripts/goap-orchestrator.sh execute [action] # Execute next action in plan
./scripts/goap-orchestrator.sh verify # Check CI + ADR parity + LOC gate
./scripts/goap-orchestrator.sh complete [action] # Mark action complete
Work is organized into waves — groups of independent actions that can execute in parallel via swarm agents.
Wave N: [action-a, action-b, action-c] ← parallel via swarm
├─ agent-1 → feat/action-a → PR #X
├─ agent-2 → feat/action-b → PR #Y
└─ agent-3 → feat/action-c → PR #Z
→ Merge order: independent first, then dependency-aware
For each wave, dispatch agents using the actor tool:
# Phase 1: Parallel exploration
explore-1 → audit action-a affected files
explore-2 → audit action-b affected files
# Phase 2: Parallel implementation
general-1 → implement action-a on feat/action-a
general-2 → implement action-b on feat/action-b
# Phase 3: Sequential merge
merge action-a PR → rebase action-b → merge action-b PR
gh pr merge --auto on stacked PRs (rebase cancellation loop)| File | Purpose |
|---|---|
plans/GOAP_STATE.md | Canonical world state (YAML) |
plans/ACTIONS.md | Action queue with preconditions/effects |
plans/GOAP_ORCHESTRATOR.md | Per-session orchestrator state |
progress/LEARNINGS.md | Cross-session learnings |
progress/PROGRESS.md | Chronological progress notes |
After each action completes:
status: complete in ACTIONS.mdaction_last_completed in GOAP_STATE.md (exactly once)progress/LEARNINGS.md if new patterns discoveredBefore merging, run ./scripts/pr-triage.sh to check:
references/dependency-graph.md — Issue dependency analysisreferences/action-templates.md — Reusable action patternsreferences/wave-execution.md — Multi-agent wave execution templateConfigure and troubleshoot npm OIDC Trusted Publishing for GitHub Actions. Use when npm publish fails with E404, OIDC errors, or provenance issues.
GitHub release management, crates.io trusted publishing, npm provenance, and GitHub Pages documentation. Use when creating releases, publishing packages, or deploying docs.
Git commit conventions, validation gates, and CI/CD workflows. Use when committing changes, verifying gates, or working with GitHub Actions.
Validate merge readiness with atomic commits and GitHub Actions checks using gh CLI; use for pre-merge verification and CI truth validation.
Apply TRIZ inventive principles to solve problems that seem to have no good solution. Use after triz-analysis has identified contradictions.
Implement or refactor Rust in this repository. Use when writing new modules, modifying existing source files, or adding features to the chaotic_semantic_memory crate.