mindsystem-cc 3.2.2 → 3.3.0

package/mindsystem/workflows/transition.md

@@ -60,8 +60,6 @@ cat .planning/config.json 2>/dev/null
 
 **If all plans complete:**
 
-<if mode="yolo">
-
 ```
 ⚡ Auto-approved: Transition Phase [X] → Phase [X+1]
 Phase [X] complete — all [Y] plans finished.
@@ -71,16 +69,6 @@ Proceeding to mark done and advance...
 
 Proceed directly to cleanup_handoff step.
 
-</if>
-
-<if mode="interactive" OR="custom with gates.confirm_transition true">
-
-Ask: "Phase [X] complete — all [Y] plans finished. Ready to mark done and move to Phase [X+1]?"
-
-Wait for confirmation before proceeding.
-
-</if>
-
 **If plans incomplete:**
 
 **SAFETY RAIL: always_confirm_destructive applies here.**
@@ -409,8 +397,6 @@ Read ROADMAP.md to get the next phase's name and goal.
 
 **If next phase exists:**
 
-<if mode="yolo">
-
 ```
 Phase [X] marked complete.
 
@@ -421,41 +407,10 @@ Next: Phase [X+1] — [Name]
 
 Exit skill and invoke SlashCommand("/ms:plan-phase [X+1]")
 
-</if>
-
-<if mode="interactive" OR="custom with gates.confirm_transition true">
-
-```
-## ✓ Phase [X] Complete
-
----
-
-## ▶ Next Up
-
-**Phase [X+1]: [Name]** — [Goal from ROADMAP.md]
-
-`/ms:plan-phase [X+1]`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ms:discuss-phase [X+1]` — gather context first
-- `/ms:research-phase [X+1]` — investigate unknowns
-- Review roadmap
-
----
-```
-
-</if>
-
 ---
 
 **Route B: Milestone complete (all phases done)**
 
-<if mode="yolo">
-
 ```
 Phase {X} marked complete.
 
@@ -466,35 +421,6 @@ Phase {X} marked complete.
 
 Exit skill and invoke SlashCommand("/ms:complete-milestone {version}")
 
-</if>
-
-<if mode="interactive" OR="custom with gates.confirm_transition true">
-
-```
-## ✓ Phase {X}: {Phase Name} Complete
-
-🎉 Milestone {version} is 100% complete — all {N} phases finished!
-
----
-
-## ▶ Next Up
-
-**Complete Milestone {version}** — archive and prepare for next
-
-`/ms:complete-milestone {version}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- Review accomplishments before archiving
-
----
-```
-
-</if>
-
 </step>
 
 </process>

package/mindsystem/workflows/verify-work.md

@@ -552,7 +552,7 @@ git stash push -m "mocks-batch-{N}"
 ```
 Task(
   prompt="""
-You are a GSD verify-fixer. Investigate this issue, find the root cause, implement a fix, and commit it.
+You are a Mindsystem verify-fixer. Investigate this issue, find the root cause, implement a fix, and commit it.
 
 ## Issue
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindsystem-cc",
-  "version": "3.2.2",
+  "version": "3.3.0",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "mindsystem-cc": "bin/install.js"

package/scripts/generate-adhoc-patch.sh

@@ -0,0 +1,79 @@
+#!/bin/bash
+#
+# generate-adhoc-patch.sh
+# Generates a patch file from an adhoc commit, excluding documentation and generated files.
+#
+# Usage: ./scripts/generate-adhoc-patch.sh <commit-hash> <output-path>
+# Example: ./scripts/generate-adhoc-patch.sh abc123f .planning/adhoc/2026-01-26-fix-bug.patch
+
+set -e
+
+# --- Configuration ---
+# Same exclusions as generate-phase-patch.sh
+EXCLUSIONS=(
+  # Documentation
+  '.planning'
+
+  # Flutter/Dart generated
+  '*.g.dart'
+  '*.freezed.dart'
+  '*.gr.dart'
+  'generated'
+  '.dart_tool'
+
+  # Next.js/TypeScript generated
+  'node_modules'
+  '.next'
+  'dist'
+  'build'
+  '*.d.ts'
+  '.turbo'
+
+  # Common build artifacts
+  '*.lock'
+)
+
+# --- Parse arguments ---
+COMMIT_HASH="$1"
+OUTPUT_PATH="$2"
+
+# --- Validation ---
+if [ -z "$COMMIT_HASH" ] || [ -z "$OUTPUT_PATH" ]; then
+  echo "Error: Commit hash and output path required"
+  echo "Usage: $0 <commit-hash> <output-path>"
+  exit 1
+fi
+
+# --- Find git root ---
+GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
+if [ -z "$GIT_ROOT" ]; then
+  echo "Error: Not in a git repository"
+  exit 1
+fi
+cd "$GIT_ROOT"
+
+# --- Verify commit exists ---
+if ! git rev-parse "$COMMIT_HASH" >/dev/null 2>&1; then
+  echo "Error: Commit $COMMIT_HASH not found"
+  exit 1
+fi
+
+# --- Build exclusion arguments ---
+EXCLUDE_ARGS=""
+for pattern in "${EXCLUSIONS[@]}"; do
+  EXCLUDE_ARGS="$EXCLUDE_ARGS ':!$pattern'"
+done
+
+# --- Generate diff from parent commit to specified commit ---
+eval "git diff \"${COMMIT_HASH}^\" \"$COMMIT_HASH\" -- . $EXCLUDE_ARGS" > "$OUTPUT_PATH"
+
+# --- Check result ---
+if [ ! -s "$OUTPUT_PATH" ]; then
+  rm -f "$OUTPUT_PATH"
+  echo "No implementation changes outside excluded patterns"
+  echo "Patch skipped"
+  exit 0
+fi
+
+PATCH_LINES=$(wc -l < "$OUTPUT_PATH" | tr -d ' ')
+echo "Generated: $OUTPUT_PATH ($PATCH_LINES lines)"

package/scripts/ms-lookup/uv.lock

@@ -67,23 +67,6 @@ wheels = [
     { url = "https://files.pythonhosted.org/packages/8a/0e/97c33bf5009bdbac74fd2beace167cab3f978feb69cc36f1ef79360d6c4e/exceptiongroup-1.3.1-py3-none-any.whl", hash = "sha256:a7a39a3bd276781e98394987d3a5701d0c4edffb633bb7a5144577f82c773598", size = 16740, upload-time = "2025-11-21T23:01:53.443Z" },
 ]
 
-[[package]]
-name = "gsd-lookup"
-version = "1.0.0"
-source = { editable = "." }
-dependencies = [
-    { name = "diskcache" },
-    { name = "httpx" },
-    { name = "typer" },
-]
-
-[package.metadata]
-requires-dist = [
-    { name = "diskcache", specifier = ">=5.6.0" },
-    { name = "httpx", specifier = ">=0.25.0" },
-    { name = "typer", specifier = ">=0.9.0" },
-]
-
 [[package]]
 name = "h11"
 version = "0.16.0"
@@ -151,6 +134,23 @@ wheels = [
     { url = "https://files.pythonhosted.org/packages/b3/38/89ba8ad64ae25be8de66a6d463314cf1eb366222074cfda9ee839c56a4b4/mdurl-0.1.2-py3-none-any.whl", hash = "sha256:84008a41e51615a49fc9966191ff91509e3c40b939176e643fd50a5c2196b8f8", size = 9979, upload-time = "2022-08-14T12:40:09.779Z" },
 ]
 
+[[package]]
+name = "ms-lookup"
+version = "1.0.0"
+source = { editable = "." }
+dependencies = [
+    { name = "diskcache" },
+    { name = "httpx" },
+    { name = "typer" },
+]
+
+[package.metadata]
+requires-dist = [
+    { name = "diskcache", specifier = ">=5.6.0" },
+    { name = "httpx", specifier = ">=0.25.0" },
+    { name = "typer", specifier = ">=0.9.0" },
+]
+
 [[package]]
 name = "pygments"
 version = "2.19.2"

package/commands/ms/discuss-milestone.md

@@ -1,48 +0,0 @@
----
-name: ms:discuss-milestone
-description: Gather context for next milestone through adaptive questioning
----
-
-<objective>
-Help you figure out what to build in the next milestone through collaborative thinking.
-
-Purpose: After completing a milestone, explore what features you want to add, improve, or fix. Features first — scope and phases derive from what you want to build.
-Output: Context gathered, then routes to /ms:new-milestone
-</objective>
-
-<execution_context>
-@~/.claude/mindsystem/references/principles.md
-@~/.claude/mindsystem/workflows/discuss-milestone.md
-</execution_context>
-
-<context>
-**Load project state first:**
-@.planning/STATE.md
-
-**Load project:**
-@.planning/PROJECT.md
-
-**Load milestones (if exists):**
-@.planning/MILESTONES.md
-</context>
-
-<process>
-1. Verify previous milestone complete (or acknowledge active milestone)
-2. Present context from previous milestone (accomplishments, phase count)
-3. Follow discuss-milestone.md workflow with **ALL questions using AskUserQuestion**:
-   - Use AskUserQuestion: "What do you want to add, improve, or fix?" with feature categories
-   - Use AskUserQuestion to dig into features they mention
-   - Use AskUserQuestion to help them articulate what matters most
-   - Use AskUserQuestion for decision gate (ready / ask more / let me add context)
-4. Hand off to /ms:new-milestone with gathered context
-
-**CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.**
-</process>
-
-<success_criteria>
-
-- Project state loaded and presented
-- Previous milestone context summarized
-- Milestone scope gathered through adaptive questioning
-- Context handed off to /ms:new-milestone
-  </success_criteria>

package/commands/ms/linear.md

@@ -1,195 +0,0 @@
----
-name: ms:linear
-description: Interact with Linear API to create, update, and manage issues
-argument-hint: "[action or description]"
-allowed-tools:
-  - Read
-  - Bash
-  - AskUserQuestion
----
-
-<objective>
-Conversational interface to Linear for fast issue management. Primary use case: user describes work → ask high-impact questions → create ticket immediately.
-
-**Speed over polish.** Get tickets into Linear quickly. Don't over-engineer descriptions or explore solutions.
-
-**No codebase exploration unless explicitly requested.** Work from user's description only. Do NOT launch agents, explore files, or analyze code unless the user explicitly asks for it.
-</objective>
-
-<execution_context>
-@~/.claude/mindsystem/scripts/ms-linear-wrapper.sh
-</execution_context>
-
-<cli_reference>
-**CLI location:** `~/.claude/mindsystem/scripts/ms-linear-wrapper.sh`
-
-**Commands:**
-| Command | Usage | Purpose |
-|---------|-------|---------|
-| `create` | `create "<title>" [-d desc] [-p priority] [-e estimate] [--parent ID] [--project name] [--no-project]` | Create issue |
-| `update` | `update <ID> [-t title] [-d desc] [-p priority]` | Update fields |
-| `done` | `done <ID>` | Mark completed |
-| `state` | `state <ID> "<name>"` | Change state |
-| `break` | `break <ID> --issues '[{...}]' [--project name] [--no-project]` | Create sub-issues |
-| `get` | `get <ID>` | Fetch details |
-| `states` | `states` | List workflow states |
-| `projects` | `projects` | List available projects |
-
-**Priority values:** 0=None, 1=Urgent, 2=High, 3=Normal, 4=Low
-
-**T-shirt to estimate mapping:**
-- XS → 1, S → 2, M → 3, L → 5, XL → 8
-
-**Project handling:**
-- `--project "Name"` — Assign to project by name (overrides config default)
-- `--no-project` — Don't assign to any project
-- If neither specified, uses `projectId` from `.linear.json` if present
-</cli_reference>
-
-<config_format>
-`.linear.json` in project root:
-
-```json
-{
-  "teamId": "uuid-of-linear-team",
-  "projectId": "uuid-of-linear-project (optional)",
-  "defaultPriority": 3,
-  "defaultLabels": []
-}
-```
-
-- `teamId` — Required. Your Linear team UUID.
-- `projectId` — Optional. Default project for new issues. Can be overridden with `--project` or `--no-project`.
-</config_format>
-
-<process>
-
-<step name="parse_intent">
-**Parse the command to determine intent:**
-
-| Pattern | Intent | Action |
-|---------|--------|--------|
-| `done <ID>` | Mark complete | Execute `done` directly |
-| `state <ID> "<name>"` | Change state | Execute `state` directly |
-| `get <ID>` | Fetch details | Execute `get` directly |
-| `states` | List states | Execute `states` directly |
-| `projects` | List projects | Execute `projects` directly |
-| `update <ID> <text>` | Update issue | Execute `update` with parsed fields |
-| `break <ID>` + user provides sub-issues | Break into sub-issues | Execute `break` with user's list |
-| `<ID> <description>` | Create sub-issue | Go to create flow with parent |
-| `<description>` | Create issue | Go to create flow |
-| (empty) | No input | Ask what they want to do |
-
-Issue ID pattern: 2-4 uppercase letters followed by hyphen and numbers (e.g., `ABC-123`, `PROJ-42`).
-</step>
-
-<step name="direct_commands">
-**For direct commands (done, state, get, states, projects, update):**
-
-Execute CLI and format output.
-
-```bash
-~/.claude/mindsystem/scripts/ms-linear-wrapper.sh [command] [args] --json-pretty
-```
-
-Parse JSON response and present result:
-- Success: Show identifier, title, new state, and URL
-- For `projects`: List projects grouped by team
-- Error: Show error message and suggestions
-</step>
-
-<step name="create_flow">
-**For create/sub-issue — FAST PATH:**
-
-1. **Parse input for hints:**
-   - Title from first sentence or quoted text
-   - Priority hints: "urgent", "high priority", "low priority", "blocker"
-   - Estimate hints: "XS", "S", "M", "L", "XL", "small", "medium", "large"
-   - Parent ID if pattern `<ID> <description>`
-   - Project hints: "in [Project]", "for [Project]", "(project: [Name])", "[Project] project"
-
-2. **Infer priority and estimate** from the description:
-   - Bug fixes, blockers → High/Urgent
-   - Small tweaks, copy changes → Low priority, XS/S estimate
-   - New features → Normal priority, M estimate
-   - Large features, refactors → Normal priority, L/XL estimate
-
-3. **Ask UP TO 4 questions in ONE AskUserQuestion call:**
-
-   Combine these into a single batch:
-
-   **Confirmation question:** Show inferred priority/estimate, ask to confirm or adjust
-
-   **High-impact domain questions (pick 1-3 most relevant):**
-   - Scope clarification: "Should this [specific behavior] or [alternative]?"
-   - Edge cases: "What should happen when [edge case]?"
-   - Acceptance criteria: "What's the minimum for this to be done?"
-   - Context: "Is this related to [existing feature/area]?"
-
-   Skip questions with obvious answers from description. If description is very clear, may only need confirmation.
-
-   If project not specified and multiple projects exist, include project selection.
-
-4. **Create immediately after answers:**
-
-   ```bash
-   ~/.claude/mindsystem/scripts/ms-linear-wrapper.sh create "[title]" \
-     -d "[description with user's answers incorporated]" -p [priority] -e [estimate] \
-     [--parent ID] [--project "Name"] [--no-project] --json-pretty
-   ```
-
-5. **Format result:**
-
-   ```
-   Created: **[identifier]** — [title]
-   Project: [project name]
-   [url]
-   ```
-</step>
-
-<step name="break_flow">
-**For breaking down issues:**
-
-User provides the sub-issues in conversation. Do NOT propose or generate sub-issues.
-
-1. **Get sub-issue list from user** (they specify titles/estimates in their message)
-
-2. **Build JSON and execute:**
-
-   ```bash
-   ~/.claude/mindsystem/scripts/ms-linear-wrapper.sh break [ID] \
-     --issues '[{"title":"...","estimate":3},{"title":"...","estimate":2}]' --json-pretty
-   ```
-
-3. **Format result:**
-
-   ```
-   Created N sub-issues under [parent-identifier]:
-   - **[ID-1]** — [title 1]
-   - **[ID-2]** — [title 2]
-   ```
-</step>
-
-<step name="error_handling">
-**Handle errors gracefully:**
-
-- **MISSING_API_KEY:** Explain how to set LINEAR_API_KEY
-- **MISSING_CONFIG:** Explain how to create .linear.json
-- **ISSUE_NOT_FOUND:** Suggest checking the identifier
-- **STATE_NOT_FOUND:** List available states from `states` command
-- **PROJECT_NOT_FOUND:** List available projects from `projects` command
-
-Always parse JSON error response and present human-friendly message with suggestions.
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Intent correctly parsed from input
-- [ ] Direct commands execute immediately without questions
-- [ ] Create flow asks max 4 questions in ONE AskUserQuestion call
-- [ ] No codebase exploration unless user explicitly requests it
-- [ ] Issue created immediately after user answers questions
-- [ ] CLI output parsed and formatted for readability
-- [ ] Errors handled with helpful suggestions
-</success_criteria>

package/mindsystem/templates/milestone-context.md

@@ -1,93 +0,0 @@
-# Milestone Context Template
-
-Template for `.planning/MILESTONE-CONTEXT.md` - temporary handoff file from discuss-milestone to create-milestone.
-
-**Purpose:** Persist milestone discussion context so `/clear` can be used between commands. This file is consumed by `/ms:new-milestone` and deleted after the milestone is created.
-
----
-
-## File Template
-
-```markdown
-# Milestone Context
-
-**Generated:** [date]
-**Status:** Ready for /ms:new-milestone
-
-<features>
-## Features to Build
-
-[Features identified during discussion - the substance of this milestone]
-
-- **[Feature 1]**: [description]
-- **[Feature 2]**: [description]
-- **[Feature 3]**: [description]
-
-</features>
-
-<scope>
-## Scope
-
-**Suggested name:** v[X.Y] [Theme Name]
-**Estimated phases:** [N]
-**Focus:** [One sentence theme/focus]
-
-</scope>
-
-<phase_mapping>
-## Phase Mapping
-
-[How features map to phases - rough breakdown]
-
-- Phase [N]: [Feature/goal]
-- Phase [N+1]: [Feature/goal]
-- Phase [N+2]: [Feature/goal]
-
-</phase_mapping>
-
-<constraints>
-## Constraints
-
-[Any constraints or boundaries mentioned during discussion]
-
-- [Constraint 1]
-- [Constraint 2]
-
-</constraints>
-
-<notes>
-## Additional Context
-
-[Anything else captured during discussion that informs the milestone]
-
-</notes>
-
----
-
-*This file is temporary. It will be deleted after /ms:new-milestone creates the milestone.*
-```
-
-<guidelines>
-**This is a handoff artifact, not permanent documentation.**
-
-The file exists only to pass context from `discuss-milestone` to `create-milestone` across a `/clear` boundary.
-
-**Lifecycle:**
-1. `/ms:discuss-milestone` creates this file at end of discussion
-2. User runs `/clear` (safe now - context is persisted)
-3. `/ms:new-milestone` reads this file
-4. `/ms:new-milestone` uses context to populate milestone
-5. `/ms:new-milestone` deletes this file after successful creation
-
-**Content should include:**
-- Features identified (the core of what to build)
-- Suggested milestone name/theme
-- Rough phase mapping
-- Any constraints or scope boundaries
-- Notes from discussion
-
-**Content should NOT include:**
-- Technical analysis (that comes during phase research)
-- Detailed phase specifications (create-milestone handles that)
-- Implementation details
-</guidelines>

package/scripts/ms-linear/ms_linear/__init__.py

@@ -1,3 +0,0 @@
-"""ms-linear CLI tool for Linear integration."""
-
-__version__ = "1.0.0"

package/scripts/ms-linear/ms_linear/__main__.py

@@ -1,6 +0,0 @@
-"""Entry point for python -m ms_linear."""
-
-from ms_linear.cli import app
-
-if __name__ == "__main__":
-    app()