write-plan

Convert specifications into implementation plans with architecture decisions and data contracts.

1|Updated Apr 29, 2026

Search Tags:#planning #specification #implementation #software architecture #data contract

Ready to run

npx skills add https://github.com/g-bastianelli/nuthouse --skill write-plan-g-bastianelli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-plan
Source: https://github.com/g-bastianelli/nuthouse/tree/main/acid-prophet/skills/write-plan
Command: npx skills add https://github.com/g-bastianelli/nuthouse --skill write-plan-g-bastianelli

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the transition from approved specifications to executable implementation plans and data contracts, ensuring clarity and efficiency in software development.

Core Features & Use Cases

Spec-to-Plan Conversion: Automatically generate a detailed implementation plan from an approved specification.
File-Level Architecture: Define file-level architecture decisions, typed API/data contracts, and a validation scenario.
Quickstart Documentation: Create a quickstart scenario to validate feature functionality.
Use Case: When an engineer has an approved spec and needs to plan the implementation before writing code.

Quick Start

Use the 'write-plan' skill on your spec located at 'docs/acid-prophet/specs/my-spec.md' to generate an implementation plan.

Frequently Asked Questions about write-plan

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

FAQPage Schema

How do I convert a software specification into an implementation plan?▼

To convert a specification into an implementation plan, you need a tool that processes approved specs alongside codebase analysis to generate file-level architecture decisions and typed data contracts for development.

What is a data contract in software architecture planning?▼

A data contract in software architecture planning defines typed API agreements between components. It is generated during the spec-to-plan conversion to ensure implementation clarity and structural consistency across file-level architecture decisions.

When do I need to generate file-level architecture decisions before coding?▼

You need to generate file-level architecture decisions during the pre-implementation stage of software development, specifically when transitioning from an approved specification to an executable implementation plan.

How to create a quickstart scenario to validate feature functionality?▼

To create a quickstart validation scenario, apply a spec-to-plan conversion tool on your approved specification. This automatically generates the required documentation and validation scenarios from your codebase analysis.

Does spec-to-plan conversion work without analyzing the existing codebase?▼

No, spec-to-plan conversion requires input from both spec frontmatter and codebase analysis. Without analyzing the existing codebase, the tool cannot generate accurate file-level architecture decisions or typed data contracts.

What is the best way to transition approved specs into executable plans?▼

The best way to transition approved specs into executable plans is using an automated spec-to-plan conversion tool. It streamlines the process by outputting implementation plans, architecture decisions, and quickstart validation scenarios directly from your specifications.