claude

forgeplan-orchestra

Runs one tracked task end to end on whatever issue tracker a project uses — Orchestra, Jira, Linear, GitHub Issues — through seven gated stages, and carries the Orchestra MCP reference (field model, failure modes, query recipes) as a separate skill free of this ecosystem. Use when the board should tell the truth about work in flight: picking a task that can actually be started, keeping its checklist honest while the work happens, proving each acceptance line, and reporting what was NOT done alongside what was. Full history in CHANGELOG.md.

4 on GitHubby ForgePlanv3.6.0MITupdated 12 days agoworkflow
/

Plugin forgeplan-orchestra from marketplace ForgePlan-marketplace in ForgePlan/marketplace. Commands read from the repo's manifest — 12 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (3)

  • orchestra-mcp

    Field guide to the Orchestra MCP server — what its tools actually do, and how they fail when they fail silently. Use when a call returned success but nothing changed, a query returned an empty or wrong count, `failedFields` appeared, a delete or a read hung, a field write did not stick, or you need

  • task-cycle

    This skill should be used when the user asks "what should I do next", "take this task", "start on X", "close the task", "update the status", "move it to done", "what is blocked", "what is ready", "file a task", "add a checklist", "report on the task", or mentions a task board, issue, ticket, status

  • unified-workflow

    Agentic RAG router for the Forgeplan + Orchestra + Claude Code unified workflow knowledge base. Routes questions to the correct section.

Slash commands (2)

  • /forgeplan-orchestra:session

    Session Start Protocol with Inbox Pattern. Restores context, collects signals from Orchestra/Git/Forgeplan, triages inbox, recommends next action.

  • /forgeplan-orchestra:sync

    Bidirectional sync between Forgeplan artifacts and Orchestra tasks. Shows diff, proposes actions, waits for confirmation.

Subagents (2)

  • orchestra-advisor

    EN: Background advisor that suggests Orchestra task sync actions when Forgeplan commands are used. HOOK-triggered after forgeplan CLI output — proposes creating/updating Orchestra tasks to mirror artifact lifecycle. Non-blocking: all suggestions are optional, never acted on autonomously. RU: Фоновый

  • task-runner

    Methodology: the seven-stage gated task cycle (orient → read → claim → work → evidence → report → close) per the `task-cycle` skill + CRUD-R-A Profile B-orchestrator scoped to the TRACKER, not to forgeplan. Tracker-agnostic: it resolves which tracker this project uses from the project's own configur

Hooks (1)

  • PostToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/forge-sync-hint.sh"

View source on GitHub forgeplan.dev

More from ForgePlan/marketplace

All 24 plugins →

Flagship workflow plugin of the ForgePlan ecosystem — the skills, templates and authoring contract the rest of the marketplace is written against: the smith methodology router (14 contexts), the agent-authoring guide every forgeplan-aware agent follows, and the gate, cleanup and insight skills that keep a pipeline honest. Use when you want the methodology itself rather than one specialist — deciding how to approach a task, gating an artifact before activation, or authoring a new agent to the house canon. Full history in CHANGELOG.md.

44 skills · 1 agent · hooks

4

Professional specialist agents: security and prompt-injection review, PII detection, architecture and staff-level system review, the pre-activation guardian gate, ADR and specification authors, research analysts and infrastructure roles. Use when a task needs a named expert rather than a generalist — an OWASP/STRIDE pass, an architectural fitness review, a decision recorded as an ADR, or the last gate before an artifact is activated. Full history in CHANGELOG.md.

30 agents

4

CANVAS design-system-to-code methodology: a coordinator walks a Pencil design through capture, audit, norm-check, vectorize and assemble, dispatching every phase and every verifier as a separate isolated context with a blocking generator-is-not-verifier gate at each handoff, plus a fail-closed hook that blocks source writes until the token contract is active. Use when a design system has to become working components in the project's own framework, with visual parity and token fidelity proven rather than asserted. Full history in CHANGELOG.md.

6 skills · 4 commands · 8 agents · hooks

4

Builds a navigable map of a project — zones, nodes and verified edges — as a `map.json`, through an eight-agent pipeline (scan -> extract -> verify -> emit -> validate) where every stage runs in a fresh isolated context and a deterministic guardian script, not an LLM, is the sole authority on whether the result can be trusted. Use when you need a structural view of a large or unfamiliar repository that a file tree cannot give, or when a project's forgeplan artifact graph should be shown alongside its code. Not a documentation generator: an edge is either sourced from the artifact graph or proven by a grep, and an unproven one is dropped rather than shipped as noise. Full history in CHANGELOG.md.

3 skills · 4 commands · 8 agents · hooks

4

fpl-hsmem

claude

Project-scoped cross-session memory for Hindsight API >=0.10.2 and <0.11.0. Use when a repository explicitly opts in via .hindsight.json; hooks default off, enrichment is operator-gated, and BankGate is client safety, not server authorization.

10 skills · 1 agent · 1 MCP server · hooks

4

Brownfield extraction pack — turns legacy code and documents into a structured forgeplan graph through a discover agent and twelve extraction skills (ubiquitous language, use cases, invariants, causal links, scenarios, knowledge-graph curation, reproducibility). Use when taking over an undocumented codebase and the first problem is not what to build but what is already there and why it is that way. Full history in CHANGELOG.md.

12 skills

4

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain forgeplan-orchestra?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins24 plugins