writing-plans

Transform design specifications into bite-sized TDD implementation tasks with exact file paths and code snippets.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/leadmind-ai/leadmind-ai-website --skill writing-plans-leadmind-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/leadmind-ai/leadmind-ai-website/tree/main/.claude/skills/chef-de-projet/writing-plans
Command: npx skills add https://github.com/leadmind-ai/leadmind-ai-website --skill writing-plans-leadmind-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transformer des specs ou un design doc en plan d'implémentation complet et actionnable. Rédiger chaque tâche comme si l'ingénieur n'avait aucun contexte sur le codebase : chemins exacts, code complet, commandes de test, sortie attendue. Tâches bite-sized. DRY. YAGNI. TDD. Commits fréquents.

Core Features & Use Cases

  • Transformer des specs ou un design doc en plan d'implémentation complet et actionnable.
  • Rédiger chaque tâche comme si l'ingénieur n'avait aucun contexte sur le codebase : chemins exacts, code complet, commandes de test, sortie attendue.
  • Tâches bite-sized. DRY. YAGNI. TDD. Commits fréquents.
  • Annoncer le démarrage avec une phrase d'introduction: "J'utilise le skill writing-plans pour créer le plan d'implémentation."
  • Sauvegarder dans : docs/plans/YYYY-MM-DD-<nom-fonctionnalite>.md
  • Lire les templates dans references/ (template-entete-plan.md et template-structure-tache.md) avant de commencer.

Quick Start

Fournissez les specs ou le design document et demandez au skill de générer un plan d’implémentation détaillé, étape par étape, prêt à être exécuté.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a design doc into actionable implementation tasks?

To turn a design doc into actionable implementation tasks, decompose specs into bite-sized steps with exact file paths, complete code snippets, test commands, and commit-ready outputs aligned with TDD.

How do I generate a TDD implementation plan from a PRD?

Generating a TDD implementation plan from a PRD involves reading the specifications, decomposing them into bite-sized tasks, validating the steps, and structuring frequent commits with complete code and tests.

What is the best way to break down software specifications for developers?

The best way to break down software specifications is to write each task assuming no codebase context, providing exact file paths, full code snippets, expected outputs, and test commands.

Does writing-plans work without existing codebase context?

Yes, writing-plans works without existing codebase context by design. It generates self-contained implementation steps detailing exact file paths, complete code, and test commands for engineers.

What templates are required to create a step-by-step coding plan?

Creating a step-by-step coding plan requires header and task structure templates stored in the references directory, which standardize the generated implementation plan's formatting.