mindsystem-cc 3.0.0

package/mindsystem/workflows/generate-mocks.md

@@ -0,0 +1,187 @@
+<purpose>
+Generate framework-specific mock code for manual UAT testing. Creates override files with toggle flags and minimal production hooks.
+
+Called by verify-work workflow when a test batch requires mock state.
+</purpose>
+
+<philosophy>
+**Mocks are temporary scaffolding.**
+
+They exist only as uncommitted changes during testing. They enable reaching UI states that require specific backend conditions (premium user, error states, empty lists, loading states).
+
+**Principles:**
+- Minimal footprint: One override file + minimal hooks
+- Easy removal: Delete file, remove imports, done
+- Framework-appropriate: Match project conventions
+- User-controlled: Clear toggle instructions
+</philosophy>
+
+<framework_detection>
+
+**Step 1: Read PROJECT.md**
+```bash
+cat .planning/PROJECT.md 2>/dev/null | head -50
+```
+
+**Step 2: Verify with config files**
+
+| Check | Indicates |
+|-------|-----------|
+| `pubspec.yaml` exists | Flutter |
+| `package.json` has `"react"` or `"next"` | React/Next.js |
+| `package.json` has `"react-native"` | React Native |
+| `package.json` has `"vue"` | Vue |
+
+**Step 3: Determine file locations**
+
+| Framework | Override File | Import Pattern |
+|-----------|---------------|----------------|
+| Flutter | `lib/test_overrides.dart` | `import 'package:{app}/test_overrides.dart';` |
+| React/Next.js | `src/testOverrides.ts` | `import { testOverrides } from '@/testOverrides';` |
+| React Native | `src/testOverrides.ts` | `import { testOverrides } from '../testOverrides';` |
+| Vue | `src/testOverrides.ts` | `import { testOverrides } from '@/testOverrides';` |
+
+</framework_detection>
+
+<override_file_pattern>
+
+**Structure:**
+
+```
+// Test Overrides - DELETE THIS FILE BEFORE COMMITTING
+// Used for manual UAT testing only
+
+// === STATE FLAGS ===
+// Set to true to enable mock state
+
+{flag declarations based on mock_type}
+
+// === MOCK DATA ===
+// Returned when flags are true
+
+{mock data structures}
+
+// === RESET ===
+// Call to disable all overrides
+
+{reset function}
+```
+
+**Flag naming convention:**
+- `force{State}` for boolean flags (e.g., `forcePremiumUser`, `forceErrorState`)
+- `mock{DataType}` for mock data (e.g., `mockUserData`, `mockErrorMessage`)
+
+</override_file_pattern>
+
+<production_hook_pattern>
+
+**Minimal hooks at service/repository layer:**
+
+```
+// Check override BEFORE real implementation
+if (testOverrides.force{State}) {
+  return testOverrides.mock{Data};
+}
+
+// Real implementation continues here...
+```
+
+**Placement:**
+- In services/repositories, not UI components
+- At the data fetch point, not the render point
+- Single if-check, no complex branching
+
+**Marking:**
+```
+// TEST OVERRIDE - Remove before commit
+if (testOverrides.forceError) {
+  throw testOverrides.mockError;
+}
+```
+
+</production_hook_pattern>
+
+<mock_types>
+
+Common mock types and what they enable:
+
+| Mock Type | Enables Testing | Typical Flags |
+|-----------|-----------------|---------------|
+| `error_state` | Error messages, retry UI, fallback displays | `forceError`, `mockErrorMessage` |
+| `premium_user` | Premium badges, gated features, upgrade prompts | `forcePremium`, `mockPremiumData` |
+| `empty_response` | Empty states, placeholder UI, "no results" | `forceEmpty` |
+| `loading_state` | Loading spinners, skeleton screens | `forceLoading`, `mockLoadingDelay` |
+| `offline` | Offline UI, cached data, sync indicators | `forceOffline` |
+
+</mock_types>
+
+<toggle_instructions_template>
+
+**Format for each mock state:**
+
+```markdown
+**To enable {state_name}:**
+1. Open `{override_file_path}`
+2. Set `{flag_name} = true`
+3. {Hot reload command or restart instruction}
+4. Verify: {What user should see to confirm mock is active}
+
+**To disable:**
+1. Set `{flag_name} = false`
+2. {Hot reload / restart}
+```
+
+**Framework-specific apply instructions:**
+
+| Framework | Apply Changes |
+|-----------|---------------|
+| Flutter | Hot reload (r in terminal) or hot restart (R) |
+| React/Next.js (dev) | Auto hot reload on save |
+| React Native | Shake device → Reload, or `r` in Metro |
+| Vue (dev) | Auto hot reload on save |
+
+</toggle_instructions_template>
+
+<spawn_mock_generator>
+
+When verify-work needs mocks:
+
+```
+Task(
+  prompt="""
+You are generating test mocks for manual UI verification.
+
+## Context
+
+Project type: {detected_framework}
+Phase: {phase_name}
+Mock type needed: {mock_type}
+
+## Tests requiring this mock
+
+{test_list_with_expected_behavior}
+
+## Requirements
+
+1. Create override file at standard location for this framework
+2. Add minimal hooks to relevant services (if needed)
+3. Provide clear toggle instructions
+4. Write all files to disk
+
+Follow the patterns from @~/.claude/mindsystem/workflows/generate-mocks.md
+""",
+  subagent_type="ms-mock-generator",
+  description="Generate {mock_type} mocks"
+)
+```
+
+</spawn_mock_generator>
+
+<success_criteria>
+- [ ] Framework correctly detected
+- [ ] Override file created at standard location
+- [ ] Minimal hooks added (only if needed)
+- [ ] Toggle instructions clear and complete
+- [ ] Files written to disk (uncommitted)
+- [ ] Easy to remove (clear cleanup path)
+</success_criteria>

package/mindsystem/workflows/list-phase-assumptions.md

@@ -0,0 +1,178 @@
+<purpose>
+Surface Claude's assumptions about a phase before planning, enabling users to correct misconceptions early.
+
+Key difference from discuss-phase: This is ANALYSIS of what Claude thinks, not INTAKE of what user knows. No file output - purely conversational to prompt discussion.
+</purpose>
+
+<process>
+
+<step name="validate_phase" priority="first">
+Phase number: $ARGUMENTS (required)
+
+**If argument missing:**
+
+```
+Error: Phase number required.
+
+Usage: /ms:list-phase-assumptions [phase-number]
+Example: /ms:list-phase-assumptions 3
+```
+
+Exit workflow.
+
+**If argument provided:**
+Validate phase exists in roadmap:
+
+```bash
+cat .planning/ROADMAP.md | grep -i "Phase ${PHASE}"
+```
+
+**If phase not found:**
+
+```
+Error: Phase ${PHASE} not found in roadmap.
+
+Available phases:
+[list phases from roadmap]
+```
+
+Exit workflow.
+
+**If phase found:**
+Parse phase details from roadmap:
+
+- Phase number
+- Phase name
+- Phase description/goal
+- Any scope details mentioned
+
+Continue to analyze_phase.
+</step>
+
+<step name="analyze_phase">
+Based on roadmap description and project context, identify assumptions across five areas:
+
+**1. Technical Approach:**
+What libraries, frameworks, patterns, or tools would Claude use?
+- "I'd use X library because..."
+- "I'd follow Y pattern because..."
+- "I'd structure this as Z because..."
+
+**2. Implementation Order:**
+What would Claude build first, second, third?
+- "I'd start with X because it's foundational"
+- "Then Y because it depends on X"
+- "Finally Z because..."
+
+**3. Scope Boundaries:**
+What's included vs excluded in Claude's interpretation?
+- "This phase includes: A, B, C"
+- "This phase does NOT include: D, E, F"
+- "Boundary ambiguities: G could go either way"
+
+**4. Risk Areas:**
+Where does Claude expect complexity or challenges?
+- "The tricky part is X because..."
+- "Potential issues: Y, Z"
+- "I'd watch out for..."
+
+**5. Dependencies:**
+What does Claude assume exists or needs to be in place?
+- "This assumes X from previous phases"
+- "External dependencies: Y, Z"
+- "This will be consumed by..."
+
+Be honest about uncertainty. Mark assumptions with confidence levels:
+- "Fairly confident: ..." (clear from roadmap)
+- "Assuming: ..." (reasonable inference)
+- "Unclear: ..." (could go multiple ways)
+</step>
+
+<step name="present_assumptions">
+Present assumptions in a clear, scannable format:
+
+```
+## My Assumptions for Phase ${PHASE}: ${PHASE_NAME}
+
+### Technical Approach
+[List assumptions about how to implement]
+
+### Implementation Order
+[List assumptions about sequencing]
+
+### Scope Boundaries
+**In scope:** [what's included]
+**Out of scope:** [what's excluded]
+**Ambiguous:** [what could go either way]
+
+### Risk Areas
+[List anticipated challenges]
+
+### Dependencies
+**From prior phases:** [what's needed]
+**External:** [third-party needs]
+**Feeds into:** [what future phases need from this]
+
+---
+
+**What do you think?**
+
+Are these assumptions accurate? Let me know:
+- What I got right
+- What I got wrong
+- What I'm missing
+```
+
+Wait for user response.
+</step>
+
+<step name="gather_feedback">
+**If user provides corrections:**
+
+Acknowledge the corrections:
+
+```
+Got it. Key corrections:
+- [correction 1]
+- [correction 2]
+
+This changes my understanding significantly. [Summarize new understanding]
+```
+
+**If user confirms assumptions:**
+
+```
+Great, assumptions validated.
+```
+
+Continue to offer_next.
+</step>
+
+<step name="offer_next">
+Present next steps:
+
+```
+What's next?
+1. Discuss context (/ms:discuss-phase ${PHASE}) - Let me ask you questions to build comprehensive context
+2. Plan this phase (/ms:plan-phase ${PHASE}) - Create detailed execution plans
+3. Re-examine assumptions - I'll analyze again with your corrections
+4. Done for now
+```
+
+Wait for user selection.
+
+If "Discuss context": Note that CONTEXT.md will incorporate any corrections discussed here
+If "Plan this phase": Proceed knowing assumptions are understood
+If "Re-examine": Return to analyze_phase with updated understanding
+</step>
+
+</process>
+
+<success_criteria>
+- Phase number validated against roadmap
+- Assumptions surfaced across five areas: technical approach, implementation order, scope, risks, dependencies
+- Confidence levels marked where appropriate
+- "What do you think?" prompt presented
+- User feedback acknowledged
+- Clear next steps offered
+</success_criteria>

package/mindsystem/workflows/map-codebase.md

@@ -0,0 +1,289 @@
+<purpose>
+Orchestrate parallel codebase mapper agents to analyze codebase and produce structured documents in .planning/codebase/
+
+Each agent has fresh context, explores a specific focus area, and **writes documents directly**. The orchestrator only receives confirmation + line counts, then writes a summary.
+
+Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
+</purpose>
+
+<philosophy>
+**Why dedicated mapper agents:**
+- Fresh context per domain (no token contamination)
+- Agents write documents directly (no context transfer back to orchestrator)
+- Orchestrator only summarizes what was created (minimal context usage)
+- Faster execution (agents run simultaneously)
+
+**Document quality over length:**
+Include enough detail to be useful as reference. Prioritize practical examples (especially code patterns) over arbitrary brevity.
+
+**Always include file paths:**
+Documents are reference material for Claude when planning/executing. Always include actual file paths formatted with backticks: `src/services/user.ts`.
+</philosophy>
+
+<process>
+
+<step name="check_existing" priority="first">
+Check if .planning/codebase/ already exists:
+
+```bash
+ls -la .planning/codebase/ 2>/dev/null
+```
+
+**If exists:**
+
+```
+.planning/codebase/ already exists with these documents:
+[List files found]
+
+What's next?
+1. Refresh - Delete existing and remap codebase
+2. Update - Keep existing, only update specific documents
+3. Skip - Use existing codebase map as-is
+```
+
+Wait for user response.
+
+If "Refresh": Delete .planning/codebase/, continue to create_structure
+If "Update": Ask which documents to update, continue to spawn_agents (filtered)
+If "Skip": Exit workflow
+
+**If doesn't exist:**
+Continue to create_structure.
+</step>
+
+<step name="create_structure">
+Create .planning/codebase/ directory:
+
+```bash
+mkdir -p .planning/codebase
+```
+
+**Expected output files:**
+- STACK.md (from tech mapper)
+- INTEGRATIONS.md (from tech mapper)
+- ARCHITECTURE.md (from arch mapper)
+- STRUCTURE.md (from arch mapper)
+- CONVENTIONS.md (from quality mapper)
+- TESTING.md (from quality mapper)
+- CONCERNS.md (from concerns mapper)
+
+Continue to spawn_agents.
+</step>
+
+<step name="spawn_agents">
+Spawn 4 parallel ms-codebase-mapper agents.
+
+Use Task tool with `subagent_type="ms-codebase-mapper"` and `run_in_background=true` for parallel execution.
+
+**CRITICAL:** Use the dedicated `ms-codebase-mapper` agent, NOT `Explore`. The mapper agent writes documents directly.
+
+**Agent 1: Tech Focus**
+
+Task tool parameters:
+```
+subagent_type: "ms-codebase-mapper"
+run_in_background: true
+description: "Map codebase tech stack"
+```
+
+Prompt:
+```
+Focus: tech
+
+Analyze this codebase for technology stack and external integrations.
+
+Write these documents to .planning/codebase/:
+- STACK.md - Languages, runtime, frameworks, dependencies, configuration
+- INTEGRATIONS.md - External APIs, databases, auth providers, webhooks
+
+Explore thoroughly. Write documents directly using templates. Return confirmation only.
+```
+
+**Agent 2: Architecture Focus**
+
+Task tool parameters:
+```
+subagent_type: "ms-codebase-mapper"
+run_in_background: true
+description: "Map codebase architecture"
+```
+
+Prompt:
+```
+Focus: arch
+
+Analyze this codebase architecture and directory structure.
+
+Write these documents to .planning/codebase/:
+- ARCHITECTURE.md - Pattern, layers, data flow, abstractions, entry points
+- STRUCTURE.md - Directory layout, key locations, naming conventions
+
+Explore thoroughly. Write documents directly using templates. Return confirmation only.
+```
+
+**Agent 3: Quality Focus**
+
+Task tool parameters:
+```
+subagent_type: "ms-codebase-mapper"
+run_in_background: true
+description: "Map codebase conventions"
+```
+
+Prompt:
+```
+Focus: quality
+
+Analyze this codebase for coding conventions and testing patterns.
+
+Write these documents to .planning/codebase/:
+- CONVENTIONS.md - Code style, naming, patterns, error handling
+- TESTING.md - Framework, structure, mocking, coverage
+
+Explore thoroughly. Write documents directly using templates. Return confirmation only.
+```
+
+**Agent 4: Concerns Focus**
+
+Task tool parameters:
+```
+subagent_type: "ms-codebase-mapper"
+run_in_background: true
+description: "Map codebase concerns"
+```
+
+Prompt:
+```
+Focus: concerns
+
+Analyze this codebase for technical debt, known issues, and areas of concern.
+
+Write this document to .planning/codebase/:
+- CONCERNS.md - Tech debt, bugs, security, performance, fragile areas
+
+Explore thoroughly. Write document directly using template. Return confirmation only.
+```
+
+Continue to collect_confirmations.
+</step>
+
+<step name="collect_confirmations">
+Wait for all 4 agents to complete.
+
+Use TaskOutput tool to collect confirmations from each agent.
+
+**Expected confirmation format from each agent:**
+```
+## Mapping Complete
+
+**Focus:** {focus}
+**Documents written:**
+- `.planning/codebase/{DOC1}.md` ({N} lines)
+- `.planning/codebase/{DOC2}.md` ({N} lines)
+
+Ready for orchestrator summary.
+```
+
+**What you receive:** Just file paths and line counts. NOT document contents.
+
+If any agent failed, note the failure and continue with successful documents.
+
+Continue to verify_output.
+</step>
+
+<step name="verify_output">
+Verify all documents created successfully:
+
+```bash
+ls -la .planning/codebase/
+wc -l .planning/codebase/*.md
+```
+
+**Verification checklist:**
+- All 7 documents exist
+- No empty documents (each should have >20 lines)
+
+If any documents missing or empty, note which agents may have failed.
+
+Continue to commit_codebase_map.
+</step>
+
+<step name="commit_codebase_map">
+Commit the codebase map:
+
+```bash
+git add .planning/codebase/*.md
+git commit -m "$(cat <<'EOF'
+docs: map existing codebase
+
+- STACK.md - Technologies and dependencies
+- ARCHITECTURE.md - System design and patterns
+- STRUCTURE.md - Directory layout
+- CONVENTIONS.md - Code style and patterns
+- TESTING.md - Test structure
+- INTEGRATIONS.md - External services
+- CONCERNS.md - Technical debt and issues
+EOF
+)"
+```
+
+Continue to offer_next.
+</step>
+
+<step name="offer_next">
+Present completion summary and next steps.
+
+**Get line counts:**
+```bash
+wc -l .planning/codebase/*.md
+```
+
+**Output format:**
+
+```
+Codebase mapping complete.
+
+Created .planning/codebase/:
+- STACK.md ([N] lines) - Technologies and dependencies
+- ARCHITECTURE.md ([N] lines) - System design and patterns
+- STRUCTURE.md ([N] lines) - Directory layout and organization
+- CONVENTIONS.md ([N] lines) - Code style and patterns
+- TESTING.md ([N] lines) - Test structure and practices
+- INTEGRATIONS.md ([N] lines) - External services and APIs
+- CONCERNS.md ([N] lines) - Technical debt and issues
+
+
+---
+
+## ▶ Next Up
+
+**Initialize project** — use codebase context for planning
+
+`/ms:new-project`
+
+<sub>`/clear` first → fresh context window</sub>
+
+---
+
+**Also available:**
+- Re-run mapping: `/ms:map-codebase`
+- Review specific file: `cat .planning/codebase/STACK.md`
+- Edit any document before proceeding
+
+---
+```
+
+End workflow.
+</step>
+
+</process>
+
+<success_criteria>
+- .planning/codebase/ directory created
+- 4 parallel ms-codebase-mapper agents spawned with run_in_background=true
+- Agents write documents directly (orchestrator doesn't receive document contents)
+- TaskOutput used to collect confirmations only
+- All 7 codebase documents exist
+- Clear completion summary with line counts
+- User offered clear next steps in GSD style
+</success_criteria>