Route milestone acceptance (Layer A/B) and final delivery. Milestone delivery stops at user-invisible milestone-scoped IT; final delivery may start after any Layer B green—1 feature milestone skips portfolio unit/IT and runs full-project E2E; ≥2 runs full unit + project IT + full-project E2E. Thin router over…
Use when working with Granoflow tasks, Task Work/Delivery, waiting for user input, weekly/monthly reviews, review cards, long-term work memory, project lifecycle boards, milestone Plan acceptance packs, project E2E SoT, long-task run continuity, workflow-jargon glosses, Local HTTP API setup, or dissatisfaction with…
Use when a user explicitly asks to review, summarize, or journal one day in Granoflow, including mood or efficiency notes. Owns the daily-review display, conversation/confirmation, write, and readback flow.
Final-stage E2E after integration is green—visible-window UI humanpath coverage from Project Work, author missing journeys, auto-fix bugs, live-window screenshots under temp/ shown to the user. Headless widget tests forbidden; no window fails closed. Not servicepath-only integration.
Use when a user asks to initialize Granoflow, optionally import data from Cursor, Codex, Hermes, or another agent, install recommended external capabilities during first-run onboarding, or perform agent history import, project and monthly milestone setup, task extraction, review-card candidate extraction, and…
Run a standard integration-test campaign—orchestrate a minimal shared-session servicepath suite (cross-module real I/O, UI clicks not required), AI auto-drives until green, triage code vs test failures, plain-language closing summary. Not E2E UI/screenshot campaigns and not task-local write-only IT.
Charter, decompose coverage, coordinate execution, replan, integrate, and accept one active Granoflow milestone after milestone and child-task entities exist. Does not batch-create milestones or author task titles/descriptions.
After Project Work (and frontend Design Baseline plus App Shell) are ready, plan and create Granoflow milestones singly or in batch. Stops when milestone entities exist; does not charter, author tasks, or execute. Prefer granoflow-portfolio-orchestrator for full portfolio-plus-tasks setup.
Persistently run one Granoflow milestone with provider-neutral workers, bounded leases, progress checkpoints, anti-livelock handling, interaction waits, and evidence-gated completion.
After Project Definition Done, create the full milestone portfolio then quality-author every milestone's tasks via skeleton coverage and createone loops. Hands off to milestone-coordination or task-orchestrator for Analysis and execution.
Initialize or refine a Granoflow software project—AI self-checks Project Work, user browse-confirms Engineering Acceptance Pack (folder structure required), user-selects Design Spec/Shell when UI applies—then hand off to milestone/task skills. Activate with "Initialize this project" / "Define this project" /…
Own the single project-local orchestration SoT at temp/project-sot.yaml. Create, lint, and regenerate it from the Granoflow App when missing, wiped, or intentionally refreshed. Use on long/unattended runs, host-wake resume, and when the user asks to rebuild Project SoT. Not an E2E test runner.
Use when an agent searches, links, creates, or modifies Granoflow review cards. Owns similarity lookup, AI filtering, universal front/back and note defaults, preview, confirmation, controlled writes, and readback.
Audit and recommend optimizations for bundled Granoflow MCP skills using the skill-polish family safely: default is read-only report + human confirm before any polish/validate apply. Activate with "orchestrate MCP skills", "audit granoflow skills", or "skill polish plan for this MCP". Not a product task orchestrator…
Create Granoflow tasks singly or via orchestrated batch—skeleton tables in batch, full title and description one task at a time with task-authoring-quality-contract. Does not run Analysis, Plan, or execution.
Infer task lifecycle intent from conversation context and orchestrate Granoflow capture, analysis, planning, execution, delivery, and completion through one short interface.
★not rated 0 1mo agoA38 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: