writing-plans

Create structured Markdown project plans in docs/plans/ with templates and status tracking.

1|Updated Jul 20, 2022
One-click install
npx skills add https://github.com/fruch/coodie --skill writing-plans-fruch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/fruch/coodie/tree/main/.github/skills/writing-plans
Command: npx skills add https://github.com/fruch/coodie --skill writing-plans-fruch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a standardized, structured approach to creating comprehensive project plans, ensuring clarity, trackability, and actionable steps for any initiative.

Core Features & Use Cases

  • Standardized Templates: Offers templates for Feature-Parity and Documentation plans.
  • Structured Sections: Enforces key sections like Goal, Table of Contents, Gap Analysis, Implementation Phases, and Test Plans.
  • Status Tracking: Integrates conventions for tracking progress using emojis and checklists.
  • Automation Integration: Supports linking PRs to plan phases for automated workflow triggers.
  • Use Case: When initiating a new feature development, use this Skill to generate a Feature-Parity plan that outlines the gaps, implementation phases, and testing strategy, ensuring all stakeholders are aligned.

Quick Start

Use the writing-plans skill to create a new feature-parity plan for the 'user-authentication' feature.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I structure a project plan in Markdown for feature development?

Structure a project plan in Markdown by defining a goal blockquote, numbered table of contents, gap analysis, implementation phases, and test plan sections. This skill enforces those conventions within the docs/plans/ directory to ensure trackability and actionable steps.

What sections should a feature-parity plan include for gap analysis?

A feature-parity plan should include structured sections for Goal, Table of Contents, Gap Analysis, Implementation Phases, and Test Plans. These standardized sections ensure all stakeholders are aligned on the gaps and testing strategy.

Can I use status tracking conventions and emojis in documentation plans?

Yes, documentation plans support status tracking conventions using emoji legends and checklists. This integrates progress tracking directly into the Markdown files to monitor phase completion.

What is the best way to track implementation phases and link PRs in project plans?

The best way to track implementation phases is using structured task tables with phase numbering and status emoji legends. This skill supports linking pull requests to plan phases for automated workflow triggers.

Does this planning approach work without external dependencies?

Yes, this planning approach works without external dependencies. It relies entirely on Markdown templates and structured conventions within the docs/plans/ directory to generate roadmaps and documentation plans.

When do I need a structured roadmap template versus a simple checklist?

You need a structured roadmap template when initiating new feature development that requires comprehensive gap analyses, phase numbering, and test plans. A simple checklist lacks the enforced structure needed to align stakeholders on implementation phases.