AI Agent Workflow Collection

By-The-Way: 작업 중 개선 제안을 즉시 수집하고 관리하는 스킬.

Create, debug, and iterate on GSD extensions (TypeScript modules that add tools, commands, event hooks, custom UI, and providers to GSD). Use when asked to build an extension, add a tool the LLM can call, register a slash command, hook into GSD events, create custom TUI components, or modify GSD behavior. Triggers on "create extension", "build extension", "add a tool", "register command", "hook into gsd", "custom tool", "gsd plugin", "gsd extension".

Break a plan or milestone brief into independently-grabbable vertical slices (tracer bullets). Produces slices in M-ROADMAP.md by default, or GitHub issues only with explicit user confirmation. Use when asked to "break this into slices", "decompose the plan", "vertical slices", "break into issues", or when a plan is ready but needs task-level decomposition. Prefers many thin slices over few thick ones; marks dependency order explicitly.

GSD 2 (Get Shit Done v2) — spec-driven autonomous development system. Use this skill when executing development tasks with GSD 2, managing milestones/slices/tasks, running auto/step/quick mode, configuring parallel orchestration, managing git worktrees, or automating via headless mode. Triggers on "gsd", "get shit done", "milestone", "slice", "auto mode", "worktree", "parallel execution".

Orchestrate GSD (Get Shit Done) projects programmatically via headless CLI. Use when an agent needs to create milestones from specs, execute software development workflows, monitor task progress, check project status, or control GSD execution (pause/stop/skip/steer). Triggers on requests to "run gsd", "create milestone", "execute project", "check gsd status", "orchestrate development", "run headless workflow", or any programmatic interaction with the GSD project management system. Essential for building orchestrators that coordinate multiple GSD workers.

Build software products autonomously via GSD headless mode. Handles the full lifecycle: write a spec, launch a build, poll for completion, handle blockers, track costs, and verify the result. Use when asked to "build something", "create a project", "run gsd", "check build status", or any task that requires autonomous software development via subprocess.

Use when about to claim work is complete, fixed, or passing, before committing changes - requires running verification commands and confirming output before making any success claims; evidence before assertions…

Synthesize the current conversation into a milestone brief (PRD). Writes to M-CONTEXT.md by default, or files a GitHub issue only with explicit user confirmation. Use when asked to "turn this into a PRD", "draft a milestone brief", "capture this context", "write it up", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.