writing-plans

Convert specifications into task-driven implementation plans with phase breakdowns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert incomplete specs or requirements into clear, executable implementation plans, ensuring nothing is overlooked.

Core Features & Use Cases

  • Plan creation: Generate phase-based task breakdowns from a written spec.
  • Cross-referencing: Link design decisions, tests, and implementation steps across files.
  • Plan storage: Save plans under plans/active/{plan-name}/implementation/ with versioned commits and repeatable structure.

Quick Start

Announce at start: "I'm using the writing-plans skill to create the implementation plan." Context: "This should be run in a dedicated worktree (created by brainstorming skill)." Save plans to: plans/active/{plan-name}/implementation/ Create multiple focused files that cross-reference each other (e.g., phase-1.md, phase-2.md, setup.md).

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert software specifications into actionable implementation plans?▼

To convert specifications into actionable implementation plans, you can generate phase-based task breakdowns that enforce frontmatter metadata and cross-reference design decisions, tests, and implementation steps across multiple files, ensuring nothing is overlooked during multi-step task execution.

What is the best way to structure task-driven plans for multi-step software engineering projects?▼

The best way to structure task-driven plans is to save multiple focused, cross-referenced files under a dedicated plans/active/{plan-name}/implementation/ directory, organizing work into phase-by-phase tasks, tests, and setup files with versioned commits.

Does this spec-to-plan workflow support TDD and DRY best practices?▼

Yes, the spec-to-plan workflow supports TDD and DRY best practices by guiding planning for phase-by-phase tasks and tests, ensuring the generated implementation plans strictly adhere to these software engineering principles throughout the multi-step process.

Can I use this approach to break down incomplete specs into executable tasks?▼

Yes, you can use this approach to break down incomplete specs into executable tasks. It converts incomplete requirements into clear, executable implementation plans, ensuring cross-referenced files and frontmatter metadata capture all necessary details.

Do I need a dedicated worktree to run this task management planning process?▼

Yes, you need a dedicated worktree to run this task management planning process. The workflow expects to be executed in a dedicated worktree created by a brainstorming skill, saving the resulting plans under the plans/active/ directory structure.