Files
skills/skills/engineering
gitadmin b9567c5e39 refactor: rename dev-workflow skill to implementation-orchestrator
The name dev-workflow described a category, not what the skill does. It
orchestrates implementation of already-planned tickets, so the new name
says that. Skill dir, docs page, name field and openai display name are
updated to match; validate-skill.sh moves with the dir and its paths are
fixed for the new depth and engineering/ layout.
2026-08-30 13:40:27 -04:00
..
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00
2026-08-27 20:14:59 -04:00

Engineering Skills

Daily code work.

User-invoked

  • commit-staged — Commit staged files with a conventional commit message.
  • grill-with-docs — Interview the user to sharpen a plan or design while creating ADRs and glossary docs.
  • implement — Implement a piece of work from a spec or set of tickets.
  • implement-isolation — Implement a piece of work from a spec or set of tickets in isolation.
  • implement-isolation-tmux — Dispatch an isolated worktree agent to implement work from a PRD or issues.
  • improve-codebase-architecture — Find and work through opportunities to deepen a codebase's architecture.
  • project-context-pack — Build a bounded project context pack for later agent work.
  • recipe-diagrams — Convert recipes into high-resolution process-flow diagrams.
  • setup-skills — Configure engineering skills, issue tracking, triage labels, and domain docs.
  • to-spec — Turn the current conversation into a spec and publish it to the issue tracker.
  • to-tickets — Break a plan or spec into tracer-bullet tickets with dependencies.
  • triage — Triage issues and external PRs through the project workflow.
  • wayfinder — Plan large work as decision tickets and resolve them step by step.

Model-invoked

  • code-review — Review changes against repository standards and the originating specification.
  • codebase-design — Design and improve deep module interfaces and seams.
  • diagnosing-bugs — Diagnose hard bugs and performance regressions.
  • domain-modeling — Build and sharpen a project's domain model.
  • lsp-code-analysis — Navigate code and analyze it semantically with LSP.
  • prototype — Build a throwaway prototype to answer a design question.
  • research — Investigate a question using high-trust sources and capture the findings.
  • resolving-merge-conflicts — Resolve an in-progress Git merge or rebase conflict.
  • tdd — Use test-driven development for features, bugs, and integration tests.
  • wizard — Generate an interactive wizard for steps only a human can perform.
  • worktrees — Manage Git worktrees in a canonical repository root.
  • write-discoverable-code — Write code agents and humans can find through plain-text search.