/spdd-reasons-canvas

Generate implementation-ready structured prompts using the built-in REASONS-Canvas framework (Requirements, Entities, Approach, Structure, Operations, Norms, Safeguards).

Input: Business context/requirement description after /spdd-reasons-canvas

Input can be provided in two ways:

1. Text description: Direct text describing the requirement
2. File/folder reference: Using @ to reference files or folders containing requirements

Examples:

# Text description
/spdd-reasons-canvas Implement user registration functionality, supporting email verification and mobile phone binding

# File reference
/spdd-reasons-canvas @requirements/user-registration.md

# Combined (text + file reference)
/spdd-reasons-canvas @requirements/user-registration.md additionally requires support for third-party OAuth login

# Multiple file references
/spdd-reasons-canvas @requirements/user-registration.md @docs/api-spec.yaml

Steps

1. Validate and consolidate business context

   a. If business context is missing, use the AskUserQuestion tool (open-ended, no preset options) to ask:

   • "Please provide the business context or requirement description (you can use text, @file references, or both)"

   IMPORTANT: Do NOT proceed without business context input.

   b. If input contains @ file/folder references:

   • Read ALL referenced files completely using the Read tool
   • For folder references, read all relevant files within the folder (.md, .txt, .yaml, .json, etc.)
   • Consolidate all file contents into a unified business context

   c. Combine all context sources:

   • Merge text descriptions with file contents
   • Preserve the complete information from all sources
   • Do NOT summarize or truncate - maintain full context integrity

   Context Integrity Check:

   • Verify all @ references were successfully read
   • If any file cannot be read, report the error and ask user to provide alternative
   • Confirm the consolidated context contains sufficient information to proceed

2. Read relevant codebase context

   • Search for related existing implementations
   • Read relevant entity classes, services, controllers
   • Understand current architecture patterns
   • Identify existing data structures and APIs

3. Apply the REASONS-Canvas Framework

   Generate fully-populated content for each of the 7 stages using the built-in construction guidance:

   ---

   R - Requirements

   Objective: Extract core problem essence and fundamental goals

   Output Format:

   ## Requirements
   [Use concise verb phrases to describe the essence of requirements]
   

   Construction Guidance:

   • Essence Extraction: Abstract what fundamental problem to solve and what value to create for whom
   • Boundary Definition: Clarify the applicable scope and limitations
   • Value Focus: Highlight business value and user benefits
   • Use Verb Phrases: "Implement...", "Create...", "Design..."
   • Avoid Feature Stacking: Don't list specific functions, abstract essential problems

   Quality Standards:

   • Core requirements summarizable in one sentence
   • Reflect business value rather than technical implementation
   • Clear problem boundaries and constraints

   ---

   E - Entities

   Objective: Build clear business entity relationship models

   Output Format:

   ## Entities
   ```mermaid
   classDiagram
   direction TB
   
   class [CoreEntity] {
       +[AttributeType] [attributeName]
       +[Method]()
   }
   
   class [RelatedEntity] {
       +[AttributeType] [attributeName]
   }
   
   class [RequestDTO] {
       +[AttributeType] [attributeName]
   }
   
   class [ResponseDTO] {
       +[AttributeType] [attributeName]
   }
   
   [CoreEntity] "[cardinality]" -- "[cardinality]" [RelatedEntity] : [relationshipDesc]
   [RequestDTO] --> [CoreEntity] : creates
   [CoreEntity] --> [ResponseDTO] : maps to
   ```
   

   Construction Guidance:

   • Entity Identification: Identify core business entities, supporting entities, DTO objects
   • Attribute Modeling: Define key attributes using "type+name" format
   • Relationship Modeling: Clarify relationship types (1:1, 1:N, N:M) and business semantics
   • Interface Design: Include key methods and static factory methods
   • Data Flow: Reflect complete flow of request→processing→response