@cregis-dev/cckit 0.4.1 → 0.5.0

package/templates/bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -1,219 +0,0 @@
----
-name: 'step-05-scope'
-description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
-
-# File References
-nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 5: MVP Scope Definition
-
-## STEP GOAL:
-
-Define MVP scope with clear boundaries and outline future vision through collaborative scope negotiation that balances ambition with realism.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative discovery tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on defining minimum viable scope and future vision
-- 🚫 FORBIDDEN to create MVP scope that's too large or includes non-essential features
-- 💬 Approach: Systematic scope negotiation with clear boundary setting
-- 📋 COLLABORATIVE scope definition that prevents scope creep
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Generate MVP scope collaboratively with user
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
-- 🚫 FORBIDDEN to proceed without user confirmation through menu
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Current document and frontmatter from previous steps, product vision, users, and success metrics already defined
-- Focus: Defining what's essential for MVP vs. future enhancements
-- Limits: Balance user needs with implementation feasibility
-- Dependencies: Product vision, user personas, and success metrics from previous steps must be complete
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Begin Scope Definition
-
-**Opening Exploration:**
-"Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
-
-**Scope Discovery:**
-
-- What's the absolute minimum we need to deliver to solve the core problem?
-- What features would make users say 'this solves my problem'?
-- How do we balance ambition with getting something valuable to users quickly?
-
-Let's start with the MVP mindset: what's the smallest version that creates real value?"
-
-### 2. MVP Core Features Definition
-
-**MVP Feature Questions:**
-Define essential features for minimum viable product:
-
-- "What's the core functionality that must work?"
-- "Which features directly address the main problem we're solving?"
-- "What would users consider 'incomplete' if it was missing?"
-- "What features create the 'aha!' moment we discussed earlier?"
-
-**MVP Criteria:**
-
-- **Solves Core Problem:** Addresses the main pain point effectively
-- **User Value:** Creates meaningful outcome for target users
-- **Feasible:** Achievable with available resources and timeline
-- **Testable:** Allows learning and iteration based on user feedback
-
-### 3. Out of Scope Boundaries
-
-**Out of Scope Exploration:**
-Define what explicitly won't be in MVP:
-
-- "What features would be nice to have but aren't essential?"
-- "What functionality could wait for version 2.0?"
-- "What are we intentionally saying 'no' to for now?"
-- "How do we communicate these boundaries to stakeholders?"
-
-**Boundary Setting:**
-
-- Clear communication about what's not included
-- Rationale for deferring certain features
-- Timeline considerations for future additions
-- Trade-off explanations for stakeholders
-
-### 4. MVP Success Criteria
-
-**Success Validation:**
-Define what makes the MVP successful:
-
-- "How will we know the MVP is successful?"
-- "What metrics will indicate we should proceed beyond MVP?"
-- "What user feedback signals validate our approach?"
-- "What's the decision point for scaling beyond MVP?"
-
-**Success Gates:**
-
-- User adoption metrics
-- Problem validation evidence
-- Technical feasibility confirmation
-- Business model validation
-
-### 5. Future Vision Exploration
-
-**Vision Questions:**
-Define the longer-term product vision:
-
-- "If this is wildly successful, what does it become in 2-3 years?"
-- "What capabilities would we add with more resources?"
-- "How does the MVP evolve into the full product vision?"
-- "What markets or user segments could we expand to?"
-
-**Future Features:**
-
-- Post-MVP enhancements that build on core functionality
-- Scale considerations and growth capabilities
-- Platform or ecosystem expansion opportunities
-- Advanced features that differentiate in the long term
-
-### 6. Generate MVP Scope Content
-
-**Content to Append:**
-Prepare the following structure for document append:
-
-```markdown
-## MVP Scope
-
-### Core Features
-
-[Core features content based on conversation]
-
-### Out of Scope for MVP
-
-[Out of scope content based on conversation, or N/A if not discussed]
-
-### MVP Success Criteria
-
-[MVP success criteria content based on conversation, or N/A if not discussed]
-
-### Future Vision
-
-[Future vision content based on conversation, or N/A if not discussed]
-```
-
-### 7. Present MENU OPTIONS
-
-**Content Presentation:**
-"I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
-
-**Here's what I'll add to the document:**
-[Show the complete markdown content from step 6]
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Read fully and follow: {advancedElicitationTask} with current scope content to optimize scope definition
-- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate MVP scope
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu with updated content
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to complete the product brief workflow.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- MVP features that solve the core problem effectively
-- Clear out-of-scope boundaries that prevent scope creep
-- Success criteria that validate MVP approach and inform go/no-go decisions
-- Future vision that inspires while maintaining focus on MVP
-- A/P/C menu presented and handled correctly with proper task execution
-- Content properly appended to document when C selected
-- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
-
-### ❌ SYSTEM FAILURE:
-
-- MVP scope too large or includes non-essential features
-- Missing clear boundaries leading to scope creep
-- No success criteria to validate MVP approach
-- Future vision disconnected from MVP foundation
-- Not presenting standard A/P/C menu after content generation
-- Appending content without user selecting 'C'
-- Not updating frontmatter properly
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/templates/bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -1,162 +0,0 @@
----
-name: 'step-06-complete'
-description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
-
-# File References
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
----
-
-# Step 6: Product Brief Completion
-
-## STEP GOAL:
-
-Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative completion tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on completion, next steps, and project guidance
-- 🚫 FORBIDDEN to generate new content for the product brief
-- 💬 Approach: Systematic completion with quality validation and next step recommendations
-- 📋 FINALIZE document and update workflow status appropriately
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Update the main workflow status file with completion information
-- 📖 Suggest potential next workflow steps for the user
-- 🚫 DO NOT load additional steps after this one (this is final)
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps
-- Focus: Completion validation, status updates, and next step guidance
-- Limits: No new content generation, only completion and wrap-up activities
-- Dependencies: All previous steps must be completed with content saved to document
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Announce Workflow Completion
-
-**Completion Announcement:**
-"🎉 **Product Brief Complete, {{user_name}}!**
-
-I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
-
-**What we've accomplished:**
-
-- ✅ Executive Summary with clear vision and problem statement
-- ✅ Core Vision with solution definition and unique differentiators
-- ✅ Target Users with rich personas and user journeys
-- ✅ Success Metrics with measurable outcomes and business objectives
-- ✅ MVP Scope with focused feature set and clear boundaries
-- ✅ Future Vision that inspires while maintaining current focus
-
-**The complete Product Brief is now available at:** `{outputFile}`
-
-This brief serves as the foundation for all subsequent product development activities and strategic decisions."
-
-### 2. Document Quality Check
-
-**Completeness Validation:**
-Perform final validation of the product brief:
-
-- Does the executive summary clearly communicate the vision and problem?
-- Are target users well-defined with compelling personas?
-- Do success metrics connect user value to business objectives?
-- Is MVP scope focused and realistic?
-- Does the brief provide clear direction for next steps?
-
-**Consistency Validation:**
-
-- Do all sections align with the core problem statement?
-- Is user value consistently emphasized throughout?
-- Are success criteria traceable to user needs and business goals?
-- Does MVP scope align with the problem and solution?
-
-### 3. Suggest Next Steps
-
-**Recommended Next Workflow:**
-Provide guidance on logical next workflows:
-
-1. `create-prd` - Create detailed Product Requirements Document
-   - Brief provides foundation for detailed requirements
-   - User personas inform journey mapping
-   - Success metrics become specific acceptance criteria
-   - MVP scope becomes detailed feature specifications
-
-**Other Potential Next Steps:**
-
-1. `create-ux-design` - UX research and design (can run parallel with PRD)
-2. `domain-research` - Deep market or domain research (if needed)
-
-**Strategic Considerations:**
-
-- The PRD workflow builds directly on this brief for detailed planning
-- Consider team capacity and immediate priorities
-- Use brief to validate concept before committing to detailed work
-- Brief can guide early technical feasibility discussions
-
-### 4. Congrats to the user
-
-"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
-
-Recap that the brief captures everything needed to guide subsequent product development:
-
-- Clear vision and problem definition
-- Deep understanding of target users
-- Measurable success criteria
-- Focused MVP scope with realistic boundaries
-- Inspiring long-term vision
-
-### 5. Suggest next steps
-
-Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Product brief contains all essential sections with collaborative content
-- All collaborative content properly saved to document with proper frontmatter
-- Workflow status file updated with completion information and timestamp
-- Clear next step guidance provided to user with specific workflow recommendations
-- Document quality validation completed with completeness and consistency checks
-- User acknowledges completion and understands next available options
-- Workflow properly marked as complete in status tracking
-
-### ❌ SYSTEM FAILURE:
-
-- Not updating workflow status file with completion information
-- Missing clear next step guidance for user
-- Not confirming document completeness with user
-- Workflow not properly marked as complete in status tracking
-- User unclear about what happens next or available options
-- Document quality issues not identified or addressed
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
-
-## FINAL WORKFLOW COMPLETION
-
-This product brief is now complete and serves as the strategic foundation for the entire product lifecycle. All subsequent design, architecture, and development work should trace back to the vision, user needs, and success criteria documented in this brief.
-
-**Congratulations on completing the Product Brief for {{project_name}}!** 🎉

package/templates/bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md

@@ -1,57 +0,0 @@
----
-name: create-product-brief
-description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
----
-
-# Product Brief Workflow
-
-**Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a product-focused Business Analyst collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, read fully and follow the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
-
-### 2. First Step EXECUTION
-
-Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.

package/templates/bmad/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -1,137 +0,0 @@
-# Domain Research Step 1: Domain Research Scope Confirmation
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user confirmation
-
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach
-- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator
-- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals
-- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- ⚠️ Present [C] continue option after scope confirmation
-- 💾 ONLY proceed when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Research type = "domain" is already set
-- **Research topic = "{{research_topic}}"** - discovered from initial discussion
-- **Research goals = "{{research_goals}}"** - captured from initial discussion
-- Focus on industry/domain analysis with web research
-- Web search is required to verify and supplement your knowledge with current facts
-
-## YOUR TASK:
-
-Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind.
-
-## DOMAIN SCOPE CONFIRMATION:
-
-### 1. Begin Scope Confirmation
-
-Start with domain scope understanding:
-"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
-
-**Domain Research Scope:**
-
-- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape
-- **Regulatory Environment**: Compliance requirements, regulations, and standards
-- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation
-- **Economic Factors**: Market size, growth trends, and economic impact
-- **Supply Chain**: Value chain analysis and ecosystem relationships
-
-**Research Approach:**
-
-- All claims verified against current public sources
-- Multi-source validation for critical domain claims
-- Confidence levels for uncertain domain information
-- Comprehensive domain coverage with industry-specific insights
-
-### 2. Scope Confirmation
-
-Present clear scope confirmation:
-"**Domain Research Scope Confirmation:**
-
-For **{{research_topic}}**, I will research:
-
-✅ **Industry Analysis** - market structure, key players, competitive dynamics
-✅ **Regulatory Requirements** - compliance standards, legal frameworks
-✅ **Technology Trends** - innovation patterns, digital transformation
-✅ **Economic Factors** - market size, growth projections, economic impact
-✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
-
-**All claims verified against current public sources.**
-
-**Does this domain research scope and approach align with your goals?**
-[C] Continue - Begin domain research with this scope
-
-### 3. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- Document scope confirmation in research file
-- Update frontmatter: `stepsCompleted: [1]`
-- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md`
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append scope confirmation:
-
-```markdown
-## Domain Research Scope Confirmation
-
-**Research Topic:** {{research_topic}}
-**Research Goals:** {{research_goals}}
-
-**Domain Research Scope:**
-
-- Industry Analysis - market structure, competitive landscape
-- Regulatory Environment - compliance requirements, legal frameworks
-- Technology Trends - innovation patterns, digital transformation
-- Economic Factors - market size, growth projections
-- Supply Chain Analysis - value chain, ecosystem relationships
-
-**Research Methodology:**
-
-- All claims verified against current public sources
-- Multi-source validation for critical domain claims
-- Confidence level framework for uncertain information
-- Comprehensive domain coverage with industry-specific insights
-
-**Scope Confirmed:** {{date}}
-```
-
-## SUCCESS METRICS:
-
-✅ Domain research scope clearly confirmed with user
-✅ All domain analysis areas identified and explained
-✅ Research methodology emphasized
-✅ [C] continue option presented and handled correctly
-✅ Scope confirmation documented when user proceeds
-✅ Proper routing to next domain research step
-
-## FAILURE MODES:
-
-❌ Not clearly confirming domain research scope with user
-❌ Missing critical domain analysis areas
-❌ Not explaining that web search is required for current facts
-❌ Not presenting [C] continue option
-❌ Proceeding without user scope confirmation
-❌ Not routing to next domain research step
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## NEXT STEP:
-
-After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md` to begin industry analysis.
-
-Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!