One-click install
npx skills add https://github.com/korwlik23/skills --skill writing-plans-korwlik23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/korwlik23/skills/tree/main/v1.1/skills/writing-plans
Command: npx skills add https://github.com/korwlik23/skills --skill writing-plans-korwlik23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning an approved design into an actionable implementation plan that a junior engineer can execute without project context or guesswork.

Core Features & Use Cases

  • Design-to-tasks conversion: Converts an approved design into bite-sized, dependency-ordered work items.
  • Verifiability built in: Ensures every task includes explicit file paths, a concrete change, and a clear verification step.
  • Workflow-aligned handoff: Produces a plan that cleanly transitions into domain implementation under the pack’s lifecycle process.

Quick Start

Tell the AI: use the writing-plans skill to write an implementation plan from my approved design, with small dependency-ordered tasks that include exact files changed and how to verify each task is done.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn an approved software design into an actionable implementation plan?

Implementation planning decomposes an approved design into small, ordered, verifiable tasks. It generates executable work items with explicit file paths, concrete changes, and per-task verification steps for a seamless coding handoff.

How do I decompose software design into verifiable coding tasks?

Task decomposition breaks software design into small, ordered work items. Each task specifies exact file paths, concrete changes, and a clear verification step, ensuring an executable plan for junior engineers without guesswork.

When do I need task decomposition for my engineering workflow?

Task decomposition is needed during the transition from design approval to coding. It applies across backend, frontend, security, database, and testing workflows, generating dependency-ordered tasks with explicit file paths and verification steps.

Does implementation planning work for backend and frontend development workflows?

Implementation planning works across backend, frontend, security, database, and testing workflows. It generates dependency-ordered tasks with explicit file paths, concrete changes, and per-task verification for each domain.

What is the best way to generate verifiable tasks with exact file paths from software design?

The best way is using implementation planning to decompose designs into verifiable tasks. It structures work items with explicit file paths, concrete changes, and verification steps, then saves the plan to a dated docs/specs file.

Why should implementation plans include per-task verification steps?

Per-task verification steps ensure each modification is checked independently. Including explicit file paths and concrete changes allows junior engineers to execute tasks without project context or guesswork.