research-plan-implement
/research-plan-implement
Research and execute a complex change across modules or sessions with a resumable local plan. Use for substantial migrations or multi-stage features, not small fixes.
- Author
- RaditteAnggoro ↗
- Repository
- agent-doctor-for-your-devices ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Research and execute a complex change across modules or sessions with a resumable local plan. Use for substantial migrations or multi-stage features, not small fixes.
Original author description
Research and execute a complex change across modules or sessions with a resumable local plan. Use for substantial migrations or multi-stage features, not small fixes.
How it works
- Locate current state
- Research and plan
- Execute or resume
- Keep a useful handoff
SKILL.md preview
--- name: research-plan-implement description: "Research and execute a complex change across modules or sessions with a resumable local plan. Use for substantial migrations or multi-stage features, not small fixes." --- # Research, Plan, Implement Maintain enough evidence and state to carry substantial work across sessions. Follow the user's current stage: research only, plan only, implement an existing plan, or complete the full change. Do not infer implementation authorization from a request for analysis. ## Locate current state Read applicable project instructions, the named plan or handoff, and the relevant current code. Check branch and working changes where Git exists. Verify that saved statements still match the files; a prior report is not proof of the current state. Reuse the project's planning conventions. For authorized implementation or a request for saved planning records, use `.agents/artifacts/<task-slug>/plan.md` and `handoff.md` if no durable location exists. Choose a new slug for unrelated work and preserve existing artifacts. For research-only or plan-only requests without saved documents in scope, return the plan and handoff information in chat. Do not create these files for a short fix. ## Research and plan Trace affected components, public contracts, persistence, and integration boundaries. Record code locations, facts, assumptions, unresolved decisions, and the smallest coherent design. Avoid a full repository survey when only one subsystem matters. Break implementation into increments that can be exercised end to end. State each increment's outcome, dependencies, likely files, and verification. Use actual project commands when known; mark unknown commands as unresolved instead of inventing them. Account for compatibility and data migration where needed. ## Execute or resume When implementation is requested, complete ready work within the authorized scope. Use the plan to guide delivery, revising it when code evidence changes a routine technical choice. Surface decisions that change the intended product or external effects. Do not ask to approve each already-authorized step. Preserve user changes. Keep independent tasks separate if using agents; delegate only when tools are actually available and inspect their output. Do not automatically create branches, worktrees, chats, commits, or external tickets. ## Keep a useful handoff When saved records are in scope, update the plan and handoff at meaningful milestones or before stopping, using [handoff-template.md](references/handoff-template.md) as a compact shape. Otherwise include the relevant record in chat. Include exact checks and remaining work, not a transcript of the conversation. Keep credentials and private payloads out of artifacts. On resumption, verify the recorded environment and code state, complete remaining authorized work, and check the original acceptance criteria. A plan file is not completion evidence.
Files in this package (3)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/handoff-template.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · RaditteAnggoro/agent-doctor-for-your-devices | 85 | MIT |
| RaditteAnggoro/skill-for-lazy-developer | 100 | MIT |
| htlin222/dotfiles | 100 | MIT |
Database snapshot: 13.11.2026 · package version e567b186a09f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100plan-change
Plan a substantial code change before implementing it. Grounds the request in the codebase, maps affected modules, contracts, consumers, data, and trust boundaries, assesses risk, and splits the work into small verifiable slices with acceptance criteria and a verification plan.… - 100implement
This skill should be used when the user asks to 'implement', 'implement a task', 'implement a plan', 'execute a plan', 'work on task', or 'start implementation'. - 100implement
Use when implementing a small or medium change directly in the current session, without a multi-task plan — via design's fast-path routing, or direct invocation ("/implement", "just implement this", "quick fix"). - 100feature-implement
[Implementation] Use when the user asks to build a feature from an idea or description with no plan file yet: research and trace the code, create and get the plan approved, build each phase with its tests, review, verify once, sync specs and docs. Existing plan: plan --mode=execute. - 100implement
Use for substantial work that adds a feature, a public contract such as an endpoint, or a multi-file behavior change; the full loop of spec, plan, batched implementation, verification and review. - 100batch-operations
Apply one change across many files safely - preview, execute, verify. Use for renames, bulk edits and migrations.