writing-plans

Generate hotl-workflow-<slug>.md implementation plans with tasks, loops, and gates.

25|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/yimwoo/hotl-plugin --skill writing-plans-yimwoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/yimwoo/hotl-plugin/tree/main/skills/writing-plans
Command: npx skills add https://github.com/yimwoo/hotl-plugin --skill writing-plans-yimwoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Writing Plans skill helps teams quickly translate design approvals into concrete implementation plans, preventing ambiguity and scope drift during execution.

Core Features & Use Cases

  • Generate a structured hotl-workflow-<slug>.md at project root to serve as the execution blueprint.
  • Break complex designs into bite-sized tasks with explicit file paths, loops, and gates.
  • Suitable for design-to-implementation handoffs and for coordinating multi-agent or human-in-the-loop workflows.

Quick Start

Create a new hotl-workflow-<slug>.md from the approved design intent and populate it with named steps, gates, and verification criteria.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I translate a design intent into an implementation plan with atomic tasks?▼

Translating a design intent into an implementation plan involves generating a structured workflow markdown file that breaks complex designs into 2-5 minute atomic, testable, and auditable tasks with explicit file paths.

What is the best way to break down design-approved workflows into bite-sized tasks?▼

Breaking down design-approved workflows requires defining named steps, loops, and gate conditions across the project root to prevent ambiguity. This ensures each step remains testable and auditable during execution.

How do I prevent scope drift during design-to-implementation handoffs?▼

Preventing scope drift during handoffs requires generating a concrete execution blueprint at the project root. This blueprint details explicit file paths, gate conditions, and verification expectations for every step.

Can I use this workflow planning approach for multi-agent coordination?▼

This workflow planning approach suits multi-agent and human-in-the-loop coordination by defining explicit gate conditions and verification expectations. Each named step remains atomic and auditable for reliable execution.

Do I need a specific file naming convention for implementation plans?▼

Implementation plans require a slug-based filename convention, specifically generating a hotl-workflow-<slug>.md file at the project root. This ensures the execution blueprint is consistently structured and accessible.

What are the limitations of generating workflow plans from design intents?▼

Generating workflow plans from design intents is limited to design-approved workflows within HOTL projects. The process requires a clear design intent upfront to properly define step structures and verification expectations.