fiberplane

fancy cli for creating fancy html docs to explain plans, work that was done, or codebase architecture. Use when user asks for a fancyplan or a fancy visual explainer.

Use when an agent is inside a remote Daytona sandbox working a Switchyard fp issue through implementation, verification, non-draft GitHub PR creation, PR babysitting, and fp property updates via REST no-clone mode.

Use when picking up, implementing, verifying, committing, or closing an fp issue in this Switchyard repo, especially when the user mentions an fp/SWYRD issue id or asks to work a task through acceptance.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (docs/patterns, docs/architecture, docs/proposals) inline as decisions crystallise. Use when user wants to stress-test a plan against the project's language and documented decisions.

Creates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform. Use when a task needs an isolated runtime, sandbox, secure compute, or Daytona SDK/API/CLI operations. Covers Python, TypeScript, Go, and Ruby SDKs.

Review code, create stories, and ensure commits are assigned to issues. Use when user asks to "review code", "assign commits", "check commits are assigned", "prepare for review", "create a story", or "write a story".

Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".

Create and break down plans into trackable issues. Use when user asks to "create a plan", "break down feature", "design implementation", "structure this work", or pastes a Linear/GitHub/Notion URL to import.

Use when a Cursor Cloud Agent is working on one or more fp issues/tickets and expected to run the full issue-to-PR loop: fetch and update fp via REST, implement code, verify, upload evidence, open a non-draft PR, handle review/CI feedback, and babysit the PR until green or a human handoff is required.

Use when picking up, implementing, verifying, committing, or closing an fp issue in this Tarmac repo, especially when the user mentions an fp/TARM issue id or asks to work a task through acceptance.

Drift doc-to-code anchor conventions. Use when editing code that is bound by drift docs, updating docs, working with drift.lock, or when drift check reports stale anchors.

Generate rich visual plans with diagrams and structured layouts. Saves locally via fp CLI. Triggers on "brainstorm", "bs", or "create a plan".