Implementation Plan
Guide for creating implementation plans. USE WHEN: planning new features, refactoring, or significant code changes.
Install
$ agentstack add skill-masayuki-kono-agent-skills-implementation-plan ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Implementation Plan Guide
A structured guide for creating comprehensive implementation plans before starting development work.
When to Use
- Planning new features or significant functionality additions
- Preparing for refactoring or architectural changes
- Documenting approach before starting complex implementation work
- Ensuring clear acceptance criteria and testing strategy
Instructions
Required Sections
1. Background and Context
Document the background and history that led to this implementation:
- Why: What problem or requirement does this address?
- Context: What is the current situation or issue?
- History: What events or changes led to this need?
- Related Issues: Any related issues, discussions, or previous attempts?
2. Acceptance Criteria
- Build and all tests must pass
- Unit tests and integration tests must be created for the implemented changes
- If project-specific verification rules exist (e.g.,
.cursor/rules/build-and-test-verification.mdc), follow them
3. Implementation Details
Document the planned approach:
- Approach: How will this be implemented?
- Changes: What files, components, or systems will be modified?
- Dependencies: Any dependencies or prerequisites?
- Testing Strategy: How will the changes be tested?
Language Requirement
All implementation plans must be written in English.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: masayuki-kono
- Source: masayuki-kono/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.