template, version, description, variables
template
version
description
variables
plan-plus
1.0
Brainstorming-enhanced PDCA Plan template with User Intent, Alternatives, and YAGNI sections
date
Creation date (YYYY-MM-DD)
project
Project name (from package.json or agents.md)
version
Project version (from package.json)
{feature} Planning Document
Summary : {One-line description}
Project : {project}
Version : {version}
Author : {author}
Date : {date}
Status : Draft
Method : Plan Plus (Brainstorming-Enhanced PDCA)
Executive Summary
Perspective
Content
Problem
{Core problem this feature solves in 1-2 sentences}
Solution
{Selected approach summary in 1-2 sentences}
Function/UX Effect
{Expected functional and UX impact}
Core Value
{Core value proposition in 1-2 sentences}
1. User Intent Discovery
1.1 Core Problem
{The core problem this feature solves — discovered through brainstorming Q1}
1.2 Target Users
User Type
Usage Context
Key Need
{User type}
{Context}
{Key need}
1.3 Success Criteria
1.4 Constraints
Constraint
Details
Impact
{Constraint}
{Details}
High/Medium/Low
2. Alternatives Explored
2.1 Approach A: {name} {Mark "— Selected" if chosen}
Aspect
Details
Summary
{One-line description}
Pros
{Advantages}
Cons
{Disadvantages}
Effort
{Estimated complexity: Low/Medium/High}
Best For
{When this approach is most suitable}
2.2 Approach B: {name}
Aspect
Details
Summary
{One-line description}
Pros
{Advantages}
Cons
{Disadvantages}
Effort
{Estimated complexity}
Best For
{When this approach is most suitable}
2.3 Decision Rationale
Selected : Approach {A/B}
Reason : {Selection reason — based on specific trade-offs}
3. YAGNI Review
3.1 Included (v1 Must-Have)
3.2 Deferred (v2+ Maybe)
Feature
Reason for Deferral
Revisit When
{Feature}
{Why not needed now}
{When to reconsider}
3.3 Removed (Won't Do)
Feature
Reason for Removal
{Feature}
{Removal reason}
4. Scope
4.1 In Scope
4.2 Out of Scope
{Excluded item 1} — (from YAGNI Review)
{Excluded item 2}
5. Requirements
5.1 Functional Requirements
ID
Requirement
Priority
Status
FR-01
{Requirement description}
High/Medium/Low
Pending
FR-02
{Requirement description}
High/Medium/Low
Pending
5.2 Non-Functional Requirements
Category
Criteria
Measurement Method
Performance
{e.g., Response time < 200ms}
{Tool/Method}
Security
{e.g., OWASP Top 10 compliance}
{Verification method}
6. Success Criteria
6.1 Definition of Done
6.2 Quality Criteria
7. Risks and Mitigation
Risk
Impact
Likelihood
Mitigation
{Risk 1}
High/Medium/Low
High/Medium/Low
{Mitigation plan}
{Risk 2}
High/Medium/Low
High/Medium/Low
{Mitigation plan}
8. Architecture Considerations
8.1 Project Level Selection
Level
Characteristics
Recommended For
Selected
Starter
Simple structure (components/, lib/, types/)
Static sites, portfolios, landing pages
Dynamic
Feature-based modules, BaaS integration (bkend.ai)
Web apps with backend, SaaS MVPs, fullstack apps
Enterprise
Strict layer separation, DI, microservices
High-traffic systems, complex architectures
8.2 Key Decisions
Decision
Options
Selected
Rationale
{Decision}
{Option list}
{Selected}
{Rationale}
8.3 Component Overview
8.4 Data Flow
9. Convention Prerequisites
9.1 Applicable Conventions
10. Next Steps
Write design document (/pdca design {feature})
Team review and approval
Start implementation (/pdca do {feature})
Appendix: Brainstorming Log
Key decisions from Plan Plus Phases 1-4.
Phase
Question
Answer
Decision
Intent
{Question summary}
{Answer summary}
{Decision}
Alternatives
{Compared items}
{Selection}
{Rationale}
YAGNI
{Reviewed items}
{Include/Exclude}
{Reason}
Version History
Version
Date
Changes
Author
0.1
{date}
Initial draft (Plan Plus)
{author}