Skill
gh-issue-bug
Generate a structured bug report for GitHub issues based on conversation context about bugs, errors, or broken functionality
@blockscoutInstall SkillBackend
Skill
/implementation-plan
Turn an approved task-analysis result into a shared technical design and coding-ready implementation handoff; use when Claude has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and
Install
$ npx -y skills add blockscout/blockscout-rs --skill implementation-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/implementation-plan
Context preview
The summary Claude sees to decide when to auto-load this skill.
Turn an approved task-analysis result into a shared technical design and coding-ready implementation handoff; use when Claude has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and
SKILL.md
implementation-plan.SKILL.mdname: implementation-plan description: Turn an approved task-analysis result into a shared technical design and coding-ready implementation handoff; use when Claude has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and `coding-task.md` before writing code disable-model-invocation: false
Implementation Plan Skill
Follow the workflow defined in @../../../.memory-bank/workflows/implementation-plan.md
Required Guardrails
- Read the existing task folder artifacts first, especially `task.md` and the selected solution.
- Re-check the current code, tests, configs, and schema paths instead of trusting earlier analysis blindly.
- Treat this as a handoff-preparation step, not a fresh solution-comparison step.
- If the chosen direction is ambiguous or stale enough to change the recommendation, stop and route the task back to analysis.
- Write the outputs into the existing `tmp/tasks/<task-name>/` folder as `implementation-plan.md` and `coding-task.md`.
- Keep the implementation plan focused on shared technical design; keep the coding task focused on actionable execution details.
Other skills on blockscout-rs.
@blockscoutInstall SkillSkill
gh-issue-improvement
Generate a structured improvement/enhancement proposal for GitHub issues based on conversation context
@blockscoutInstall SkillSkill
gh-issue-publish
Publish a GitHub issue from a markdown file in tmp/gh-issues/ created by gh-issue-bug or gh-issue-improvement skills
@blockscoutInstall SkillSkill
pr-description
Prepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot.…
@blockscoutInstall SkillSkill
research-scope
Investigate and document the intended scope of a codebase topic through interactive discussion, then persist a durable research…
@blockscoutInstall SkillSkill
solution-review
Review already-applied code changes against the original task statement or task folder artifacts under `tmp/tasks/<task-name>/`.…
@blockscoutInstall Skill