workflow

the workbench

route the actual request to the smallest useful workflow. inspect live state first; reuse the project-owned contract and evidence record. a workflow mode does not erase prior authorization or require a fresh approval for each step.

right tool firstscripts over retypingleaves the bench clean

Use for development workflow and process work -- answering technical questions, bootstrapping or planning projects, brainstorming, autonomous research loops, scenario generation, bug fixing, feature implementation, codebase scouting, retrospectives, status reports, session journals, and end-to-end ship pipelines.

methodology

  1. read trained first -- it carries the learned routing layer.
  2. classify by pipeline stage: question/context (ask, scout), planning (brainstorm, ck-plan, ck-predict, ck-scenario), implementation (bootstrap, cook, fix, vibe), verification/reporting (ck-debug, retro, watzup, journal, ship), process meta (coding-level, problem-solving, sequential-thinking, ck-autoresearch, ck-loop, ck-graphify, plans-kanban).
  3. read the owning guide and only the references needed for this task; diagnose concrete bugs before applying the fix workflow.
  4. process for process gates, orchestration for authorized delegation.

contents

procedures

procedures the guru runs, one page each. read it, then follow it.

related gurus: process, testing, review.

search pages

go to any page