ReddRadar
Agent skill
draft-plan
Produce an implementation plan at .turbo/plans/<slug>.md. Use when the user asks to "draft a plan", "draft the plan", "write an implementation plan", "plan this change", "create an implementation plan", "fill in the shell", "expand the shell", or needs a first-draft plan file before refinement.
Install this agent skill to your Project
npx add-skill https://github.com/tobihagemann/turbo/tree/main/skills/draft-plan
SKILL.md
Draft Plan
Produce an implementation plan at .turbo/plans/<slug>.md.
If a shell file path was passed, read references/fill-in-mode.md and follow its steps. Otherwise, read references/full-mode.md and follow its steps.
Rules
- Never skip the pattern survey.
- Never skip decision escalation before drafting.
- The plan file is the only output. Do not write code, scaffolding, or other project files.
- Do not run
/review-planor any review skills here. - Do not embed task tracking, skill loading, or
/finalizeinvocation in the plan file.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
tobihagemann/turbo
review-api-usage
Check API, library, and framework usage in code against official documentation and installed skill knowledge. Flags deprecated APIs, incorrect method signatures, wrong parameter types, version-incompatible patterns, and best-practice violations. Use when the user asks to "review API usage", "check API usage", "verify against docs", "check library usage", "validate API calls", "check against documentation", or "check for deprecated APIs".
tobihagemann/turbo
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR feedback", "handle review comments", "address review feedback", "respond to PR comments", "answer review questions", or "address code review".
tobihagemann/turbo
consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", "brainstorm with codex", "discuss with codex", or "chat with codex".
tobihagemann/turbo
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev infrastructure", or "tooling audit".
tobihagemann/turbo
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
tobihagemann/turbo
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
Didn't find tool you were looking for?