mindsystem-cc 3.10.0 → 3.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (47) hide show
  1. package/README.md +3 -6
  2. package/agents/ms-designer.md +8 -8
  3. package/agents/ms-executor.md +14 -163
  4. package/agents/ms-plan-checker.md +2 -3
  5. package/agents/ms-plan-writer.md +5 -11
  6. package/agents/ms-roadmapper.md +101 -16
  7. package/agents/ms-verify-fixer.md +1 -1
  8. package/commands/ms/complete-milestone.md +1 -1
  9. package/commands/ms/create-roadmap.md +126 -56
  10. package/commands/ms/design-phase.md +12 -10
  11. package/commands/ms/execute-phase.md +0 -9
  12. package/commands/ms/help.md +24 -35
  13. package/commands/ms/new-milestone.md +184 -80
  14. package/commands/ms/new-project.md +3 -3
  15. package/commands/ms/research-project.md +2 -2
  16. package/commands/ms/review-design.md +9 -5
  17. package/commands/ms/verify-work.md +1 -1
  18. package/mindsystem/references/continuation-format.md +2 -3
  19. package/mindsystem/references/design-directions.md +1 -1
  20. package/mindsystem/references/mock-patterns.md +48 -0
  21. package/mindsystem/references/plan-format.md +2 -129
  22. package/mindsystem/references/routing/between-milestones-routing.md +5 -7
  23. package/mindsystem/references/scope-estimation.md +3 -3
  24. package/mindsystem/templates/config.json +0 -2
  25. package/mindsystem/templates/design.md +1 -1
  26. package/mindsystem/templates/milestone-context.md +76 -0
  27. package/mindsystem/templates/phase-prompt.md +6 -142
  28. package/mindsystem/templates/summary.md +24 -0
  29. package/mindsystem/workflows/complete-milestone.md +27 -8
  30. package/mindsystem/workflows/execute-phase.md +35 -124
  31. package/mindsystem/workflows/execute-plan.md +12 -517
  32. package/mindsystem/workflows/generate-mocks.md +74 -0
  33. package/mindsystem/workflows/mockup-generation.md +1 -1
  34. package/mindsystem/workflows/plan-phase.md +7 -24
  35. package/mindsystem/workflows/verify-work.md +97 -17
  36. package/package.json +1 -1
  37. package/scripts/__pycache__/compare_mockups.cpython-314.pyc +0 -0
  38. package/scripts/compare_mockups.py +219 -0
  39. package/skills/flutter-code-quality/SKILL.md +1 -1
  40. package/skills/flutter-code-simplification/SKILL.md +1 -1
  41. package/skills/flutter-senior-review/AGENTS.md +1 -1
  42. package/skills/flutter-senior-review/SKILL.md +1 -1
  43. package/commands/ms/define-requirements.md +0 -128
  44. package/mindsystem/references/checkpoint-detection.md +0 -50
  45. package/mindsystem/references/checkpoints.md +0 -788
  46. package/mindsystem/workflows/create-milestone.md +0 -243
  47. package/mindsystem/workflows/discuss-milestone.md +0 -310
@@ -1,50 +0,0 @@
1
- <checkpoint_detection>
2
- Lite reference for identifying checkpoint types during task breakdown. Full checkpoint templates and examples are in the ms-plan-writer subagent.
3
-
4
- <checkpoint_types>
5
-
6
- | Type | Use When | Frequency |
7
- |------|----------|-----------|
8
- | `checkpoint:human-verify` | Claude automated work, human confirms visual/functional correctness | 90% |
9
- | `checkpoint:decision` | Human must choose between options affecting implementation | 9% |
10
- | `checkpoint:human-action` | Truly unavoidable manual step with no CLI/API (rare) | 1% |
11
-
12
- </checkpoint_types>
13
-
14
- <detection_rules>
15
-
16
- **Mark as `checkpoint:human-verify` when:**
17
- - Visual UI checks needed (layout, styling, responsiveness)
18
- - Interactive flows require human testing (click through wizard, test user flows)
19
- - Functional verification beyond automated tests (feature works as expected)
20
- - Audio/video playback, animation smoothness, accessibility
21
-
22
- **Mark as `checkpoint:decision` when:**
23
- - Technology selection (auth provider, database, library)
24
- - Architecture choices (monorepo vs separate, API patterns)
25
- - Design decisions (color scheme, layout approach)
26
- - Feature prioritization between variants
27
-
28
- **Mark as `checkpoint:human-action` when (rare):**
29
- - Email verification links (account creation)
30
- - SMS 2FA codes (phone verification)
31
- - Manual account approvals
32
- - Credit card 3D Secure flows
33
- - OAuth app approvals requiring browser
34
-
35
- </detection_rules>
36
-
37
- <automation_first_principle>
38
- **If it has CLI/API, Claude automates it. No exceptions.**
39
-
40
- Never create `checkpoint:human-action` for:
41
- - Deployments (use `vercel`, `railway`, `fly` CLI)
42
- - Database operations (use provider CLI)
43
- - Webhook setup (use APIs)
44
- - Environment files (use Write tool)
45
- - Running builds/tests (use Bash tool)
46
-
47
- The rule: Claude does everything automatable. Checkpoints verify AFTER automation, not replace it.
48
- </automation_first_principle>
49
-
50
- </checkpoint_detection>