Planning & Workflow

Review a feature plan like a founder to challenge scope and product bets

Review a plan for developer experience gaps in an interactive session before building

Review a coding plan like an engineering manager to catch risks before building

Write a weekly engineering retrospective on the team's recent work

Merge the base branch, run tests, bump the version and open a pull request

Turn a vague idea into a precise, executable spec through five phases

Write Conventional Commits messages compressed to intent only

Locate code across a repo and return path and line citations for orientation

Build feature work with strict scope, reused code and a clear stop condition

Record your quality bar in CONSTRAINTS.md and catch diffs that quietly weaken it

Structure git branches, atomic commits and pull requests for clean version history

Ship changes in thin, verifiable slices, with feature flags and tests at each step

Break a spec into ordered, estimable tasks that can be built in parallel

Manage Orca worktrees, terminals, automations and browser sessions from the CLI

Prepare GitHub pull requests with branch hygiene, commit shape, titles and test notes

Write a plan with a clear outcome and verification steps before execution starts

Send an accepted artifact to a downstream tool or team and log the export

Open a pull request that adds your local plugin to the community catalog with the gh CLI

Build a daily GitHub digest of pull requests, review requests, issues and CI runs

Resolve PR review comments and merge conflicts, then validate fixes before pushing

Plan a multi-file rewrite with clear ownership boundaries and patch-safety rules

Package an accepted plugin or artifact as a GitHub pull request for a target repo

Watch a pull request until comments, reviews and CI issues are all resolved

Read every source file in a new codebase to get up to speed fast

Write a phased implementation plan after discovering the relevant docs

Cluster a GitHub issue backlog by root cause and bundle fixes into PRs

Run a read-only standup across worktrees and PRs with one consolidation plan

Evaluate RFCs, designs and migrations from first principles before coding

Push for the simplest solution that works by reusing code and the standard library

Manage branches, resolve conflicts and run the full pull request lifecycle

Write SPARC pseudocode and architecture, then implement the design

Write mock-first, outside-in tests in the London school TDD style

Pull WakaTime coding time stats and project activity through Composio Rube MCP

Implement the tasks of an OpenSpec change one step at a time

Archive a finished OpenSpec change once its implementation is complete

Archive several completed OpenSpec changes in one pass

Create the next artifact in an OpenSpec change to keep its workflow moving

Explore ideas and requirements with a thinking partner before an OpenSpec change

Create all OpenSpec artifacts for a change in one fast-forward pass

Start a new OpenSpec change with a structured step-by-step artifact workflow

Walk through a full OpenSpec cycle on your codebase with guided narration

Turn a feature idea into a full OpenSpec proposal with design, specs and tasks

Sync delta specs from an OpenSpec change into main specs without archiving

Revise OpenSpec change plans so their artifacts stay consistent with each other

Check that an implementation matches its OpenSpec artifacts before archiving

Stress-test a plan with a hostile team that cross-critiques it before formalizing

Explore a codebase first, then write one decision-complete plan before coding

Check out a deferred repository a Factory task needs, after confirming access

Fetch and show GitHub pull request review comments for the current branch