plan-plus

name	plan-plus
classification	hybrid
classification-reason	Combines workflow automation with capability-dependent features
deprecation-risk	low
effort	high
description	Brainstorming-enhanced PDCA planning with intent discovery and YAGNI review. For a single feature's plan use /plan-plus; for grouping multiple features under one scope/budget see /sprint master-plan (v2.1.13). Triggers: plan-plus, brainstorm, plan plus, intent
argument-hint	[feature]
user-invocable	true
allowed-tools	["Read","Write","Edit","Glob","Grep","Bash","Task","TaskCreate","TaskUpdate","TaskList","AskUserQuestion"]
imports	["${PLUGIN_ROOT}/templates/plan-plus.template.md"]
next-skill	pdca design
pdca-phase	plan
task-template	[Plan Plus] {feature}

Plan Plus — Brainstorming-Enhanced PDCA Planning

Combines brainstorming's intent discovery with bkit PDCA's structured planning to produce higher-quality Plan documents through collaborative dialogue.

Overview

Plan Plus enhances the standard /pdca plan by adding 4 brainstorming phases before document generation. This ensures that user intent is fully understood, alternatives are explored, and unnecessary features are removed before any implementation begins.

When to use Plan Plus instead of /pdca plan:

• The feature has ambiguous or complex requirements
• Multiple implementation approaches are possible
• You want to ensure YAGNI compliance from the start
• The feature involves significant architectural decisions

HARD-GATE

Do NOT write any code, scaffold any project, or invoke any implementation skill until this entire process is complete and the user has approved the Plan document. This applies to EVERY feature regardless of perceived simplicity. A "simple" feature still goes through this process — the design can be short, but you MUST present it and get approval.

Process Flow

Phase 0: Context Exploration (automatic)
    ↓
Phase 1: Intent Discovery (1 question at a time)
    ↓
Phase 2: Alternatives Exploration (2-3 approaches)
    ↓
Phase 3: YAGNI Review (multiSelect verification)
    ↓
Phase 4: Incremental Design Validation (section-by-section)
    ↓
Phase 5: Plan Document Generation (plan-plus.template.md)
    ↓
Phase 6: Next Steps → /pdca design {feature}

Phase Details

Phase 0: Project Context Exploration (Automatic)

Before asking any questions, explore the current project state:

1. Read CLAUDE.md, package.json, pom.xml, etc. for project information
2. Check recent 5 git commits (understand current work direction)
3. Check existing docs/01-plan/ documents (prevent duplication)
4. Check .bkit-memory.json (check ongoing PDCA status)

Share exploration results briefly: "I've reviewed the current project state: ..."

Phase 1: Intent Discovery (Brainstorming Style)

Principle: One question at a time, prefer multiple choice

Use AskUserQuestion tool to discover the following in order:

Q1. Core Purpose

"What is the core problem this feature solves?"

• Provide 3-4 choices (inferred from project context)
• Always include a custom input option