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 `coding-task.md` before writing code

Jump to install

Repository: blockscout/blockscout-rs
Last source activity: July 23, 2026 at 11:53
Detected SKILL.md language: English
Stars: 231
Forks: 205

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/blockscout/blockscout-rs --skill implementation-plan

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name	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.

Back to search Back to installation

research-scope

Investigate the intended scope of a codebase topic through discussion with a human, propose a research-note outline, and only create a .memory-bank/research file after explicit human confirmation.

2026-08-25

implementation-plan

Turn an approved task analysis and selected solution into a technical design and coding-ready handoff under `tmp/tasks/<task-name>/`, with explicit human confirmation before the coding task is written.

2026-08-10

pr-description

Draft or refresh a reviewer-facing Markdown PR description from `tmp/tasks/<task-name>/` and the current implementation snapshot, covering functional scope, API/config, migration, testing, and follow-ups.

2026-08-10

View all from this repository

name	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.

implementation-plan

Source facts

Install options

Review the source files

Implementation Plan Skill

Required Guardrails

More from this repository

Implementation Plan Skill

Required Guardrails

More from this repository