From ork
Orchestrates multi-phase development pipelines with checkpoint/resume to handle rate limits, interruptions, and GitHub issues/commits. Saves state to .claude/pipeline-state.json after each phase.
npx claudepluginhub yonatangross/orchestkit --plugin orkThis skill is limited to using the following tools:
Rate-limit-resilient pipeline orchestrator. Saves progress to `.claude/pipeline-state.json` after every phase so long sessions survive interruptions.
Executes long-running autonomous tasks with multi-phase checkpoints, verification stack, and interruption recovery for large refactors, migrations, and features over 50% context window.
Orchestrates multi-day execution of complex tasks via milestone pipelines with plan-crafting, run-plan, review-work phases, checkpoints, and recovery.
Enforces git workflow for claudikins-kernel:execute: decomposes plans into atomic tasks per branch, two-stage reviews, batch sizing, human checkpoints to prevent parallelization issues.
Share bugs, ideas, or general feedback.
Rate-limit-resilient pipeline orchestrator. Saves progress to .claude/pipeline-state.json after every phase so long sessions survive interruptions.
| Category | Rule | Impact | Key Pattern |
|---|---|---|---|
| Phase Ordering | ${CLAUDE_SKILL_DIR}/rules/ordering-priority.md | CRITICAL | GitHub issues/commits first, file-heavy phases last |
| State Writes | ${CLAUDE_SKILL_DIR}/rules/state-write-timing.md | CRITICAL | Write after every phase, never batch |
| Mini-Commits | ${CLAUDE_SKILL_DIR}/rules/checkpoint-mini-commit.md | HIGH | Every 3 phases, checkpoint commit format |
Total: 3 rules across 3 categories
If .claude/pipeline-state.json exists: run scripts/show-status.sh to display progress, then ask to resume, pick a different phase, or restart. Load Read("${CLAUDE_SKILL_DIR}/references/resume-decision-tree.md") for the full decision tree.
If no state file exists: ask the user to describe the task, build an execution plan, write initial state via scripts/init-pipeline.sh <branch>, begin Phase 1.
{
"phases": [
{ "id": "create-issues", "name": "Create GitHub Issues", "dependencies": [], "status": "pending" },
{ "id": "commit-scaffold", "name": "Commit Scaffold", "dependencies": [], "status": "pending" },
{ "id": "write-source", "name": "Write Source Files", "dependencies": ["commit-scaffold"], "status": "pending" }
]
}
Phases with empty dependencies may run in parallel via Task sub-agents (when they don't share file writes).
.claude/pipeline-state.json — see Read("${CLAUDE_SKILL_DIR}/rules/state-write-timing.md")Read("${CLAUDE_SKILL_DIR}/rules/checkpoint-mini-commit.md")Load on demand with Read("${CLAUDE_SKILL_DIR}/references/<file>"):
| File | Content |
|---|---|
references/pipeline-state-schema.md | Full field-by-field schema with examples |
references/pipeline-state.schema.json | Machine-readable JSON Schema for validation |
references/resume-decision-tree.md | Logic for resuming, picking phases, or restarting |
scripts/init-pipeline.sh <branch> — print skeleton state JSON to stdoutscripts/show-status.sh [path] — print human-readable pipeline status (requires jq)| Decision | Recommendation |
|---|---|
| Phase granularity | One meaningful deliverable per phase (a commit, a set of issues, a feature) |
| Parallelism | Task sub-agents only for phases with empty dependencies that don't share file writes |
| Rate limit recovery | State is already saved — re-invoke /checkpoint-resume to continue |