mindsystem-cc 3.0.0 → 3.2.0

package/agents/ms-executor.md

@@ -691,7 +691,6 @@ Progress: [progress bar]
 ```markdown
 Last session: [current date and time]
 Stopped at: Completed {phase}-{plan}-PLAN.md
-Resume file: [path to .continue-here if exists, else "None"]
 ```
 
 </state_updates>

package/agents/ms-roadmapper.md

@@ -303,7 +303,6 @@ Key sections:
 - Current Position (phase, plan, status, progress bar)
 - Performance Metrics
 - Accumulated Context (decisions, todos, blockers)
-- Session Continuity
 
 ## Draft Presentation Format
 

package/bin/install.js

@@ -5,8 +5,8 @@ const path = require('path');
 const os = require('os');
 const readline = require('readline');
 
-// Colors
-const cyan = '\x1b[38;2;47;167;160m'; // #2FA7A0
+// Colors (using 256-color mode for better terminal compatibility)
+const cyan = '\x1b[38;5;37m'; // Closest to #2FA7A0 in 256-color palette
 const green = '\x1b[32m';
 const yellow = '\x1b[33m';
 const dim = '\x1b[2m';

package/commands/ms/help.md

@@ -337,28 +337,6 @@ Check project status and intelligently route to next action.
 
 Usage: `/ms:progress`
 
-### Session Management
-
-**`/ms:resume-work`**
-Resume work from previous session with full context restoration.
-
-- Use when: you paused mid-phase and want to restore context and continue.
-- Reads STATE.md for project context
-- Shows current position and recent progress
-- Offers next actions based on project state
-
-Usage: `/ms:resume-work`
-
-**`/ms:pause-work`**
-Create context handoff when pausing work mid-phase.
-
-- Use when: you need to stop mid-stream and want a reliable handoff pointer for next time.
-- Creates `.continue-here` file with current state
-- Updates STATE.md session continuity section
-- Captures in-progress work context
-
-Usage: `/ms:pause-work`
-
 ### Debugging
 
 **`/ms:debug [issue description]`**
@@ -606,14 +584,6 @@ Common options:
 /ms:check-todos api             # Filter by area
 ```
 
-**Pausing and resuming mid-phase:**
-
-```
-/ms:pause-work                # Creates a handoff pointer
-# later...
-/ms:resume-work               # Restore context and continue
-```
-
 ## Getting Help
 
 - Read `.planning/PROJECT.md` for project vision

package/commands/ms/linear.md

@@ -0,0 +1,231 @@
+---
+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>
+Provide a conversational interface to Linear for issue management. Route to the appropriate CLI command based on user intent.
+
+Apply Pareto principle: ask max 4 high-impact questions. Skip questions with obvious answers from context.
+</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 |
+| `break <ID>` | Break into sub-issues | Go to break flow |
+| `update <ID> <text>` | Update issue | Execute `update` with parsed fields |
+| `<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):**
+
+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:**
+
+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. **Ask clarifying questions (max 4, single AskUserQuestion call):**
+
+   Skip questions with obvious answers. Examples:
+   - Title clearly stated → don't ask for title
+   - Priority mentioned → don't ask for priority
+   - Simple task → skip estimate question
+   - Project mentioned → don't ask for project
+
+   Use AskUserQuestion with questions like:
+   - Priority (if not obvious from context)
+   - Estimate (if not mentioned)
+   - Project (if multiple projects exist and none specified)
+   - Description details (if ambiguous)
+
+   For project selection, first run `projects` command to get available options.
+
+3. **Show preview and confirm:**
+
+   ```
+   ## Create Issue
+
+   **Title:** [parsed title]
+   **Project:** [project name or "Team backlog"]
+   **Priority:** [priority name]
+   **Estimate:** [estimate if set]
+   **Parent:** [parent ID if sub-issue]
+
+   Create this issue?
+   ```
+
+   Use AskUserQuestion: "Create this issue?" with options:
+   - "Yes, create it"
+   - "Edit first"
+   - "Cancel"
+
+4. **Execute CLI:**
+
+   ```bash
+   ~/.claude/mindsystem/scripts/ms-linear-wrapper.sh create "[title]" \
+     -d "[description]" -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:**
+
+1. **Fetch parent issue:**
+
+   ```bash
+   ~/.claude/mindsystem/scripts/ms-linear-wrapper.sh get [ID] --json-pretty
+   ```
+
+2. **Analyze and propose sub-issues:**
+
+   Based on title and description, propose 2-5 sub-issues:
+   - Each with clear title
+   - Inherit parent's priority unless specified
+   - Suggest estimates if pattern is clear
+
+   ```
+   ## Break Down: [identifier] — [title]
+
+   Proposed sub-issues:
+   1. [Title 1] (M)
+   2. [Title 2] (S)
+   3. [Title 3] (M)
+   ```
+
+3. **Confirm with user:**
+
+   Use AskUserQuestion: "Create these sub-issues?" with options:
+   - "Yes, create all"
+   - "Let me edit the list"
+   - "Cancel"
+
+4. **Build JSON and execute:**
+
+   ```bash
+   ~/.claude/mindsystem/scripts/ms-linear-wrapper.sh break [ID] \
+     --issues '[{"title":"...","estimate":3},{"title":"...","estimate":2}]' --json-pretty
+   ```
+
+5. **Format result:**
+
+   ```
+   Created 3 sub-issues under [parent-identifier]:
+   - **[ID-1]** — [title 1]
+   - **[ID-2]** — [title 2]
+   - **[ID-3]** — [title 3]
+   ```
+</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
+- [ ] Create flow asks max 4 questions
+- [ ] User confirms before creating/updating
+- [ ] CLI output parsed and formatted for readability
+- [ ] Errors handled with helpful suggestions
+</success_criteria>

package/commands/ms/progress.md

@@ -31,7 +31,22 @@ Run /ms:new-project to start a new project.
 
 Exit.
 
-If missing STATE.md: suggest `/ms:new-project`.
+**If missing STATE.md but PROJECT.md or ROADMAP.md exist:**
+
+Reconstruct STATE.md from artifacts:
+
+1. Read PROJECT.md → Extract "What This Is" and Core Value
+2. Read ROADMAP.md → Determine phases, find current position
+3. Scan *-SUMMARY.md files → Extract recent decisions, concerns
+4. Count pending todos in .planning/todos/pending/
+
+Write reconstructed STATE.md, then proceed to "load" step.
+
+```
+"STATE.md missing. Reconstructing from artifacts..."
+```
+
+If missing both STATE.md and PROJECT.md/ROADMAP.md: suggest `/ms:new-project`.
 
 **If ROADMAP.md missing but PROJECT.md exists:**
 
@@ -354,7 +369,6 @@ Ready to plan the next milestone.
 - Phase complete but next phase not planned → offer `/ms:plan-phase [next]`
 - All work complete → offer milestone completion
 - Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/ms:resume-work`
   </step>
 
 </process>

package/commands/ms/remove-phase.md

@@ -79,8 +79,6 @@ ERROR: Cannot remove Phase {target}
 Only future phases can be removed:
 - Current phase: {current}
 - Phase {target} is current or completed
-
-To abandon current work, use /ms:pause-work instead.
 ```
 
 Exit.

package/mindsystem/templates/state.md

@@ -73,12 +73,6 @@ None yet.
 [Issues that affect future work]
 
 None yet.
-
-## Session Continuity
-
-Last session: [YYYY-MM-DD HH:MM]
-Stopped at: [Description of last completed action]
-Resume file: [Path to .continue-here*.md if exists, otherwise "None"]
 ```
 
 <purpose>
@@ -172,12 +166,6 @@ Updated after each plan completion.
 - Prefix with originating phase
 - Cleared when addressed
 
-### Session Continuity
-Enables instant resumption:
-- When was last session
-- What was last completed
-- Is there a .continue-here file to resume from
-
 </sections>
 
 <size_constraint>
@@ -219,6 +207,5 @@ The goal is "read once, know where we are" — if it's too long, that fails.
 - Current Position: Where we are now (phase, plan, status)
 - Performance Metrics: Velocity tracking
 - Accumulated Context: Recent decisions, pending todos, adhoc work, blockers
-- Session Continuity: Resume information
 
 </guidelines>

package/mindsystem/workflows/execute-plan.md

@@ -1455,7 +1455,6 @@ Update Session Continuity section in STATE.md to enable resumption in future ses
 ```markdown
 Last session: [current date and time]
 Stopped at: Completed {phase}-{plan}-PLAN.md
-Resume file: [path to .continue-here if exists, else "None"]
 ```
 
 **Size constraint note:** Keep STATE.md under 150 lines total.

package/mindsystem/workflows/transition.md

@@ -106,18 +106,6 @@ Wait for user decision.
 
 </step>
 
-<step name="cleanup_handoff">
-
-Check for lingering handoffs:
-
-```bash
-ls .planning/phases/XX-current/.continue-here*.md 2>/dev/null
-```
-
-If found, delete them — phase is complete, handoffs are stale.
-
-</step>
-
 <step name="update_roadmap">
 
 Update the roadmap file:
@@ -379,14 +367,12 @@ Update Session Continuity section in STATE.md to reflect transition completion.
 ```markdown
 Last session: [today]
 Stopped at: Phase [X] complete, ready to plan Phase [X+1]
-Resume file: None
 ```
 
 **Step complete when:**
 
 - [ ] Last session timestamp updated to current date and time
 - [ ] Stopped at describes phase completion and next phase
-- [ ] Resume file confirmed as None (transitions don't use resume files)
 
 </step>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindsystem-cc",
-  "version": "3.0.0",
+  "version": "3.2.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/ms-linear/ms_linear/__init__.py

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

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

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