writing-plans

Convert research findings into structured implementation plans with tasks and verification steps.

20|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/bostonaholic/rpikit --skill writing-plans-bostonaholic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/bostonaholic/rpikit/tree/main/skills/writing-plans
Command: npx skills add https://github.com/bostonaholic/rpikit --skill writing-plans-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex work by transforming research into a structured, verifiable implementation plan.

Core Features & Use Cases

  • Generate a detailed plan from research findings, including tasks, target files, actions, verification criteria, and risk notes.
  • Classify stakes and scope, producing a plan document at docs/plans/YYYY-MM-DD-$ARGUMENTS-plan.md.
  • Link back to existing research when available and guide collaboration between planning and implementation phases.

Quick Start

Provide a detailed implementation plan for the given task, referencing any existing research and outputting a plan document at docs/plans/YYYY-MM-DD-$ARGUMENTS-plan.md.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn research findings into an actionable implementation plan?

To turn research findings into an implementation plan, the Skill structures your findings into verifiable tasks, target files, actions, and success criteria, outputting a markdown plan document.

What is the best way to break down complex development tasks with risk management?

Breaking down complex development tasks involves classifying stakes and scope, defining target files, actions, and verification steps, while adding risk notes to guide disciplined execution.

How do I generate a deployment plan that includes verification steps and documentation?

Generating a deployment plan with verification steps involves structuring tasks with target files, actions, and success criteria, then saving the output as a dated markdown plan document.

Does this planning approach require existing research to function correctly?

This planning approach does not strictly require existing research, but it links back to available research findings to ensure the generated implementation plan is accurately grounded.

Where are the generated implementation plan documents saved?

Generated implementation plan documents are saved as markdown files at the path docs/plans/YYYY-MM-DD-$ARGUMENTS-plan.md, ensuring plans are dated and organized for future reference.

Can I use this for planning tasks that need clear success criteria and scope classification?

Yes, you can use this for planning tasks requiring clear scope classification, success criteria, task breakdown, and risk management across both planning and execution phases.