plan

Interview users to produce a phased implementation plan before coding.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/stratus/my-claude --skill plan-stratus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/stratus/my-claude/tree/main/skills/plan
Command: npx skills add https://github.com/stratus/my-claude --skill plan-stratus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams and developers align on goals by interviewing stakeholders and producing a structured implementation plan before any coding begins.

Core Features & Use Cases

  • Interview-driven goal clarification to surface boundaries and success criteria.
  • Phase-based planning with milestones, deliverables, and risk assessment.
  • Documentation guidance to capture decisions, scope, and acceptance criteria.

Quick Start

Interview the user to clarify goals and constraints, then generate a phased implementation plan before writing code.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a structured implementation plan before coding a multi-file project?

Creating a structured implementation plan involves interviewing stakeholders to clarify goals, then mapping milestones, deliverables, and acceptance criteria across distinct phases before development begins.

What is interview-driven goal clarification for feature development?

Interview-driven goal clarification is the process of questioning users to surface project boundaries, constraints, and success criteria, ensuring teams align on scope before producing phased design documentation.

How do I document milestones and acceptance criteria for a system redesign?

Documenting milestones and acceptance criteria requires capturing phased decisions, scope boundaries, and evaluation checkpoints, ensuring each system redesign milestone has clear deliverables and risk assessments.

Can I use this planning approach for multi-file projects with phased deliverables?

Yes, this planning approach suits multi-file projects by applying a phased approach with evaluation checkpoints, ensuring clear milestones and deliverables are established for each development stage.

What's the best way to align product teams and developers on project scope?

The best way to align teams is conducting user interviews to clarify requirements, producing structured documentation that captures decisions, scope, and acceptance criteria before any coding starts.

When do I need phased design documentation for requirements gathering?

You need phased design documentation when tackling feature development or system redesigns requiring clear boundaries, milestone mapping, and evaluation checkpoints to satisfy structured requirements before implementation.