step-orchestrator
Installation
SKILL.md
Step Orchestrator
Run the main agent as coordinator. It owns plan state, Markdown plan writeback, commits, and hard-blocker decisions. Subagents own only the single round they are spawned for.
Require these inputs
- Require a repo-local Markdown plan file path such as
docs/plan.mdorplans/migration.md. - Require explicit step IDs or ranges such as
3-5,7. - Require the target workspace or repository. Treat the current workspace as the default only when the user does not name another one.
- Accept tests, constraints, branch preferences, and acceptance criteria as optional additions.
- Treat an explicit request to use this skill, delegate, use subagents, or run worker/reviewer agents as permission to spawn subagents. If that permission is absent, ask before spawning.
Load references only when needed
Related skills
More from charys117/skills
oracle
>-
8notion-board
Use Notion as the primary interface for repository architecture, pipelines, modules, constants, plans, todos, issues, and commit logs. Use when Codex needs to create or update a repo-backed Notion board, answer questions from board contents, keep repo-derived content synced one-way from the repo into Notion, or save the board location locally without exposing that state in git.
1