plan-writer

Generate project specifications with competing alternatives, assumptions, and dependency mapping.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zivtech/joyus-desktop --skill plan-writer-zivtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writer
Source: https://github.com/zivtech/joyus-desktop/tree/main/.claude/skills/plan-writer
Command: npx skills add https://github.com/zivtech/joyus-desktop --skill plan-writer-zivtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents project failure by forcing the documentation of assumptions, competing alternatives, and failure modes before execution begins, ensuring that risks are visible and managed from the start.

Core Features & Use Cases

  • Competing Alternatives Analysis: Evaluates 2-3 approaches using ACH-lite to ensure the best path is chosen based on evidence rather than intuition.
  • Pre-Mortem Analysis: Generates concrete failure scenarios across multiple time horizons to identify and mitigate risks before they occur.
  • Assumption Register: Tracks every project assumption, rating them by fragility and defining mitigation strategies for high-risk bets.
  • Use Case: A team is debating between two different architectural approaches for a new feature; this Skill structures the comparison, maps dependencies, and identifies potential bottlenecks before a single line of code is written.

Quick Start

Use the plan-writer skill to create a detailed project plan for the upcoming migration of our authentication system.

Frequently Asked Questions about plan-writer

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

FAQPage Schema
How do I run a pre-mortem analysis for project risk management?

Pre-mortem analysis generates concrete failure scenarios across multiple time horizons to identify and mitigate project risks before execution begins. It forces teams to anticipate specific failure modes and document proactive mitigation strategies.

What is competing alternatives analysis for evaluating project specifications?

Competing alternatives analysis evaluates 2-3 approaches using ACH-lite methodology to ensure the best path is chosen based on evidence rather than intuition. It structures architectural comparisons by mapping dependencies and identifying bottlenecks.

How do I document project assumptions to prevent initiative failure?

Documenting project assumptions requires tracking every assumption in a register, rating them by fragility, and defining mitigation strategies for high-risk bets. This ensures risks remain visible and managed from the project's start.

Does structured backcasting work for high-consequence project planning?

Structured backcasting satisfies requirements for high-consequence initiatives requiring rigorous risk assessment and failure mode mitigation. It maps dependencies and documents competing alternatives to ensure robust project plan design.

What is the best way to evaluate competing architectural approaches before development?

Evaluating competing architectural approaches requires analyzing 2-3 alternatives using structured comparison methodologies like ACH-lite. This ensures evidence-based path selection by mapping dependencies, identifying bottlenecks, and documenting assumptions.

When should I not use proposal-critic review integration for project planning?

Proposal-critic review integration suits high-consequence initiatives requiring rigorous risk assessment rather than lightweight or low-risk tasks. It is unnecessary when projects lack complex dependencies or when failure modes carry minimal operational impact.