writing-plans

Generate step-by-step implementation plans with file modifications, code examples, and tests.

2|Updated Feb 6, 2026

Search Tags:#planning #documentation #software development #implementation #codex #task breakdown

Ready to run

npx skills add https://github.com/mistakeknot/Clavain --skill writing-plans-mistakeknot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/mistakeknot/Clavain/tree/main/skills/writing-plans
Command: npx skills add https://github.com/mistakeknot/Clavain --skill writing-plans-mistakeknot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating clear, detailed, and actionable implementation plans for software development tasks, even when starting with zero codebase context.

Core Features & Use Cases

Structured Plan Generation: Creates plans with bite-sized tasks, including file paths, code snippets, tests, and verification steps.
Context-Awareness: Incorporates prior art and institutional learnings to inform plan creation.
Execution Handoff: Recommends and facilitates the execution of the plan via various sub-skills or delegation to tools like Codex.
Use Case: When tasked with implementing a new user authentication feature, this Skill will generate a comprehensive plan detailing every file to modify, the exact code to write, and the tests to run, ensuring a smooth development process.

Quick Start

Use the writing-plans skill to create an implementation plan for the new user profile page feature.

Frequently Asked Questions about writing-plans

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

FAQPage Schema

How do I generate an implementation plan for a new software feature without existing codebase context?▼

Implementation plans for new features can be generated without prior codebase context by structuring detailed steps with specific file modifications, code examples, test cases, and verification steps. This process incorporates prior art and institutional learnings to ensure actionable task breakdown.

What is the best way to structure task breakdown documentation for software development handoff?▼

Task breakdown documentation for software development handoff is structured into bite-sized tasks including file paths, code snippets, tests, and verification steps. This structure facilitates smooth execution delegation to other skills or tools like Codex for final implementation.

Can I use generated implementation plans directly with Codex for execution?▼

Generated implementation plans can be directly handed off to Codex for execution. The plans are specifically structured to facilitate this delegation by outlining exact file modifications and verification steps required for automated task completion.

How does a detailed software implementation plan incorporate prior art and institutional learnings?▼

A detailed software implementation plan incorporates prior art and institutional learnings by using them as context to inform the creation of file modifications and code examples. This ensures the generated steps align with established development practices and institutional knowledge.

Do I need an existing codebase to create a step-by-step implementation plan for a new feature?▼

An existing codebase is not needed to create a step-by-step implementation plan for a new feature. The plan generation process assumes zero prior codebase context and independently outlines the specific file paths, code snippets, and tests required from scratch.