Planning & Workflow

Brainstorm and design before building features, components or any new plan

Execute an implementation plan step by step inside the current session

Decide how to integrate a finished branch once all tests pass

Set up an isolated git worktree before starting feature work or a plan

Turn a spec or requirements for a multi-step task into a plan before coding

Stress-test a plan with relentless questions while writing ADRs and glossary docs

Turn a spec or set of tickets into implemented code in your repository

Implement the output of to-spec and to-tickets in code

Write a pull request body that reviewers can read and merge quickly

Set review gates and ownership rules for codebases that agents mostly write

Turn one objective into a dependency-ordered plan of PR-sized build steps

Audit an existing project and close gaps in thinking, coding practice and features

Review staged changes and draft a Conventional Commits message with the right type

Choose a branching strategy and keep git history clean with rebase and conflict fixes

Triage GitHub issues, manage pull requests and releases, and watch CI with gh

Build a new feature through research, plan, TDD, review and a gated commit

Turn a spec document into a running MVP through thin vertical slices and reviews

Change an existing working feature to new behavior, updating its tests before the code

Run the gated research, plan, TDD, review and commit pipeline behind the orch skills

Annotate and approve plans or HTML drafts in a local browser canvas

Split a plan document into steps and generate the slash command to run each one

Search npm, PyPI, GitHub and MCP servers before writing custom code

Write a failing test first, then implement the smallest change that turns it green

Run commands, debug CI failures and push narrow fixes with a verified execution log

Work with GitHub pull requests, issues, reviews and repos through gh

Pressure-test a plan with an adversarial interview before you build

Plan coordinated multi-workflow work with shared data table schemas before building

Act on user feedback left on the changes in the current session

Write a commit message in the style of the repo and commit staged or unstaged changes

Open a draft pull request with the changes from the current session

Open a pull request with the changes from the current session

Set up run commands that appear on the Run button of the session

Merge a topic branch from the current session back into its base branch

Get setup steps to scaffold a complete new project in a VS Code workspace

Get setup steps to scaffold a complete new project in a VS Code workspace

Sync a branch with its upstream or publish it to a remote

Rebase a stale branch onto the latest origin and resolve conflicts

Push new changes to an existing pull request from the session

Make the smallest change that fully solves a coding task and explain it briefly

Show measured code, cost and speed savings from the ponytail benchmark

Quick reference for ponytail lazy-coding levels, skills and commands

Reconstruct why a function exists from its git history and companion files

Find dead side projects on your machine and decide which one to revive

Run CEO, design, engineering and DX reviews on a plan in sequence with auto decisions

Warn before destructive shell commands run during coding sessions

Audit the live developer experience of a tool, from setup steps to error messages

Lock file edits to one directory for the rest of a coding session

Write a weekly engineering retrospective from commit history and team trends

Warn on destructive commands and limit edits to one directory during a session