plan

Automate strategic planning with interview-driven discovery or direct plan generation.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/wmasfoe/notch-pet --skill plan-wmasfoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/wmasfoe/notch-pet/tree/main/.codex/skills/plan
Command: npx skills add https://github.com/wmasfoe/notch-pet --skill plan-wmasfoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan addresses the need for disciplined, scalable project planning by automatically deciding between an interview-driven requirements discovery flow and direct plan generation, and by coordinating a multi-pass Planner/Architect/Critic loop with RALPLAN-DR structured deliberation and review modes.

Core Features & Use Cases

  • Auto-detects whether to interview the user or plan directly based on request specificity.
  • Supports Consensus and Review modes with structured deliverables (RALPLAN-DR summaries, ADRs).
  • Facilitates multi-perspective validation and traceable decision records for product strategy, project scoping, and baseline planning.
  • Use Case: vagues ideas can be scoped into concrete milestones, acceptance criteria, and risk mitigations; review a draft plan for refinement; or run iterative drafting with interactive feedback.

Quick Start

Start by describing your goal and choose either a direct plan request or an interview-based planning workflow.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a vague project idea into an actionable plan with acceptance criteria?

To turn a vague idea into an actionable plan, you describe your goal and the system auto-detects whether to interview you for requirements or generate a plan directly. This structured workflow outputs concrete milestones, acceptance criteria, and risk mitigations.

What is the best way to document architectural decisions during project scoping?

The best way to document architectural decisions during project scoping is by generating ADR-style decision records. This process captures traceable, testable planning outputs with documentation references to ensure multi-perspective consensus.

How does multi-persona consensus planning work for product strategy?

Multi-persona consensus planning works by coordinating a multi-pass Planner, Architect, and Critic loop using structured deliberation. This validates product strategy from multiple perspectives and outputs traceable baseline plans and review summaries.

Can I use an interview-driven workflow for requirements discovery on vague requests?

Yes, you can use an interview-driven workflow for requirements discovery. The system automatically selects this interactive feedback loop when handling broad or vague requests to ensure all project requirements are properly scoped before plan generation.

Does this planning approach generate testable outputs with file references?

Yes, this planning approach generates testable outputs with file references. It satisfies requirements for traceable planning documentation by including specific file references, acceptance criteria, and detailed plan steps.

When should I use review mode versus direct plan generation for project management?

You should use review mode to refine a draft plan through iterative drafting, while direct plan generation suits concrete project scoping. The system auto-selects direct generation for specific requests and interviews for vague ideas.