wz:writing-plans

Generate ordered execution plans with tasks, milestones, and acceptance criteria.

3|1|Updated Mar 16, 2026

Search Tags:#planning #documentation #execution #phases #task-management #plan-review

Ready to run

npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-writing-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wz:writing-plans
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/writing-plans
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-writing-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Plans provides a structured way to convert approved direction, research, and design into an actionable execution plan that teams can follow to deliver results.

Core Features & Use Cases

Generates an ordered, task-based execution plan with concrete tasks, subtasks, acceptance criteria, verification steps, and cleanups.
Supports both standalone plans and run-based plans saved under .wazir/runs/latest/clarified/ or docs/plans/YYYY-MM-DD-<topic>-implementation.md.
Enables a Plan Review Loop to iteratively validate and refine the plan with stakeholders.

Quick Start

Provide an execution-grade plan after receiving clear direction, research findings, and design approval.

Frequently Asked Questions about wz:writing-plans

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

FAQPage Schema

How do I turn approved designs into an execution plan with concrete tasks?▼

To turn approved designs into an execution plan, you draft an ordered, task-based sequence detailing concrete tasks, subtasks, acceptance criteria, verification steps, and cleanups for phase-driven work.

What is the best way to structure phase-driven project plans with milestones?▼

The best way to structure phase-driven project plans is by generating an ordered sequence of explicit tasks, milestones, and acceptance criteria, ensuring every phase has defined verification steps and cleanups before moving forward.

How do I save executable project plans when no active run exists?▼

When no active run exists, you save executable project plans as standalone markdown files in the docs/plans directory using the YYYY-MM-DD-<topic>-implementation.md naming format.

Can I iteratively validate a task management plan with stakeholders before execution?▼

Yes, you can iteratively validate a task management plan with stakeholders using a Plan Review Loop, which allows you to continuously refine the ordered tasks and acceptance criteria based on stakeholder feedback before execution begins.

Do I need research findings and design approvals before drafting an implementation plan?▼

Yes, you need clear direction, research findings, and design approvals in place before drafting an implementation plan, because the process converts these finalized inputs into an actionable, execution-grade sequence of tasks.

Where are execution plans saved when integrated into an active project run?▼

When integrated into an active project run, execution plans are saved directly under the .wazir/runs/latest/clarified/ directory structure to maintain continuity with the active workflow.