@accelerationguy/accel 1.0.0

package/modules/mission-control/mission-control/tasks/insights.md

@@ -0,0 +1,73 @@
+<purpose>
+Run workspace analytics across all projects. Surfaces velocity, stalls, blocking chains, workload distribution, revenue exposure, and pending handoffs. Uses the mission-control-insights.py engine.
+</purpose>
+
+<user-story>
+As a workspace operator, I want to see analytics across all my projects at a glance, so I can make informed decisions about where to focus my time.
+</user-story>
+
+<when-to-use>
+- Before deciding what to work on next
+- During weekly groom cycles for the full picture
+- When a project feels stalled and you want to check if it's actually blocked
+- Before stakeholder updates to see revenue exposure
+- Entry point routes here via /accel insights
+</when-to-use>
+
+<steps>
+
+<step name="check_prerequisites" priority="first">
+Verify Momentum is installed and has project data.
+
+1. Check `.accel/momentum/data/projects.json` exists
+2. Check `.accel/momentum/workspace.json` exists
+3. If either is missing:
+   > "Insights requires Momentum to be installed with workspace data. Run `/accel install momentum` first."
+   Stop.
+</step>
+
+<step name="run_analytics">
+Execute the mission-control-insights analytics engine.
+
+Run via Bash:
+```bash
+python3 {workspace}/.accel/momentum/hooks/accel-insights.py
+```
+
+The script outputs:
+- **Velocity** — Drive projects sorted by plan age, phase progress, loop position
+- **Stalls** — Projects with plan age > 14 days (active, not completed/deferred)
+- **Blocking Analysis** — Grouped by blocker with revenue at risk
+- **Cross-Project Dependencies** — Dependency chain visualization
+- **Workload by Category** — Active project count per category
+- **Revenue Exposure** — All revenue-tied projects with blocked flags
+- **Pending Handoffs** — Drive satellites awaiting handoff processing
+
+Capture the full output.
+</step>
+
+<step name="strategic_summary">
+Provide a brief strategic summary based on the analytics data.
+
+Based on the analytics output, answer:
+1. What's the biggest risk right now? (revenue at risk from blocks, stalled projects)
+2. What project deserves attention based on stall duration + revenue impact?
+3. Any cross-project dependencies creating cascading blocks?
+4. One recommendation for this session based on what's actionable.
+
+Keep it concise — 5-8 lines max. This is for decision-making, not reporting.
+</step>
+
+</steps>
+
+<output>
+Full analytics output from the insights engine followed by a brief strategic summary with one actionable recommendation.
+</output>
+
+<acceptance-criteria>
+- [ ] Momentum installation verified before running
+- [ ] Analytics engine executed successfully
+- [ ] All 7 analytics sections present in output
+- [ ] Strategic summary is concise (5-8 lines)
+- [ ] Recommendation is actionable (something user can do this session)
+</acceptance-criteria>

package/modules/mission-control/mission-control/tasks/install.md

@@ -0,0 +1,194 @@
+<purpose>
+Orchestrate the installation of one or all Mission Control frameworks in dependency order. Runs each framework's npm installer via Bash, handles inter-framework wiring, and offers post-install scaffold for Momentum.
+</purpose>
+
+<user-story>
+As a Claude Code user, I want to install the Mission Control framework suite from within Claude Code, so that my workspace is fully set up with all tools properly wired and ready to use.
+</user-story>
+
+<when-to-use>
+- Setting up a brand new workspace
+- Adding a specific framework to an existing workspace
+- Re-installing or updating a framework
+- Entry point routes here via /accel install
+</when-to-use>
+
+<context>
+@frameworks/framework-registry.md
+</context>
+
+<steps>
+
+<step name="determine_scope" priority="first">
+Determine what to install.
+
+Check if the user specified a framework in their command:
+- `/accel install` (no arg) → ask what to install
+- `/accel install all` → install all 7 frameworks
+- `/accel install vector` → install Vector only
+- `/accel install vector momentum drive` → install specified frameworks
+
+If asking, present the menu:
+```
+Which frameworks do you want to install?
+
+  1. all     — Full suite (Vector → Momentum → Drive → Ignition → Forge → Radar)
+  2. vector    — Context rules engine
+  3. momentum    — Workspace lifecycle management
+  4. drive    — Project orchestration (Plan-Apply-Unify)
+  5. ignition    — Project incubation
+  6. forge — Skill builder
+  7. radar   — Security audit framework
+
+Enter names or numbers (comma-separated), or "all":
+```
+
+**Wait for response.**
+</step>
+
+<step name="check_prerequisites">
+Verify prerequisites for the selected frameworks.
+
+1. Check Node.js is available: `node --version`
+2. Check Python 3 is available: `python3 --version`
+3. Check `~/.claude/` directory exists
+
+If any check fails, report the issue and stop.
+
+For dependency-ordered install, check if dependencies are already installed:
+- Momentum requires Vector → check `~/.vector/vector.json`
+- If Vector is needed but not selected and not installed, add it automatically:
+  > "Momentum requires Vector. Adding Vector to the install queue."
+
+Report: "Prerequisites OK. Installing: {list} in order: {ordered list}"
+</step>
+
+<step name="detect_existing">
+Check what's already installed to avoid unnecessary reinstalls.
+
+For each selected framework, use the detection method from the framework registry:
+- Vector: `~/.vector/vector.json` exists?
+- Momentum: `.accel/momentum/workspace.json` exists?
+- Drive: `~/.claude/commands/drive/` exists?
+- Ignition: `~/.claude/commands/ignition/ignition.md` exists?
+- Forge: `~/.claude/commands/forge/forge.md` exists?
+- Radar: `~/.claude/radar/` exists?
+
+For each already-installed framework, ask:
+> "{Framework} is already installed. Reinstall/update? (y/n)"
+
+If user says no, skip that framework.
+If all frameworks are already installed and user skips all, report and exit.
+</step>
+
+<step name="install_frameworks">
+Install each framework in dependency order.
+
+For each framework in the install queue (ordered per registry):
+
+**Vector:**
+```bash
+npx @accel/vector --global --skip-claude-md
+```
+After install, verify: `~/.vector/vector.json` exists, `~/.claude/hooks/vector-hook.py` exists.
+
+**Momentum:**
+```bash
+npx @accel/momentum --global --workspace
+```
+After install, verify: `.accel/momentum/workspace.json` exists, `.accel/momentum/momentum-mcp/` exists.
+Note: hooks are NOT yet wired — scaffold handles that.
+
+**Drive:**
+```bash
+npx @accel/drive --global
+```
+After install, verify: `~/.claude/commands/drive/` exists.
+
+**Ignition:**
+```bash
+npx @accel/ignition
+```
+After install, verify: `~/.claude/commands/ignition/ignition.md` exists.
+
+**Forge:**
+```bash
+npx @accel/forge
+```
+After install, verify: `~/.claude/commands/forge/forge.md` exists.
+
+**Radar:**
+Radar lacks non-interactive mode. Use direct file copy from the repo or npm package:
+```bash
+# If repo available locally:
+cp -r {radar-repo}/src/* ~/.claude/radar/
+cp {radar-repo}/commands/*.md ~/.claude/commands/radar/
+# If not available, clone from GitHub first
+```
+After install, verify: `~/.claude/radar/` exists, `~/.claude/commands/radar/audit.md` exists.
+
+Report progress after each:
+> "Vector installed. (1/6)"
+> "Momentum installed. (2/6)"
+> ...
+</step>
+
+<step name="cross_framework_wiring">
+Handle inter-framework integration that individual installers don't do.
+
+1. **Drive Vector domain**: If both Vector and Drive are installed, check if vector.json has a Drive domain. If not, offer to add it:
+   > "Both Vector and Drive are installed. Want to add the Drive enforcement domain to Vector? This adds rules that protect the Plan-Apply-Unify loop integrity."
+   If yes: read the Drive domain from the drive-framework repo's `src/vector/Drive` file, parse it, and add to vector.json via the Vector MCP tools.
+
+2. **Mission Control commands**: Copy the Mission Control skill itself to `~/.claude/commands/accel/` (or the workspace `.claude/commands/accel/`) so /accel commands are available going forward.
+</step>
+
+<step name="post_install">
+Handle post-install steps.
+
+1. **Momentum scaffold**: If Momentum was installed, ask:
+   > "Momentum needs /momentum:scaffold to complete setup (wires hooks, configures operator profile). Run it now? (y/n)"
+   - If yes: invoke `/momentum:scaffold` via the Skill tool
+   - If no: "You can run /momentum:scaffold later to complete Momentum setup."
+
+2. **Verification**: Run through the install verification checklist.
+   @checklists/install-verification.md
+
+3. **Summary**: Report final state:
+   ```
+   Mission Control Installation Complete
+
+   Installed:
+     Vector     v2.0.0  ✓
+     Momentum     v3.0.1  ✓ (scaffold pending)
+     Drive     v1.2.0  ✓
+     Ignition     v1.0.0  ✓
+     Forge v1.0.0 ✓
+     Radar    v0.2.0  ✓
+
+   Next steps:
+   - Run /momentum:scaffold to complete Momentum setup (if skipped)
+   - Run /drive:init in any project to start orchestrated development
+   - Run /radar:validate to verify security tools
+   - Restart Claude Code to reload all commands
+   ```
+</step>
+
+</steps>
+
+<output>
+All selected frameworks installed, verified, and wired. User has clear next steps for any post-install configuration.
+</output>
+
+<acceptance-criteria>
+- [ ] User selected which frameworks to install
+- [ ] Prerequisites checked (Node.js, Python 3, ~/.claude/)
+- [ ] Dependencies auto-resolved (Vector added if Momentum selected)
+- [ ] Existing installs detected and user given choice to skip/update
+- [ ] Each framework installed via its official installer
+- [ ] Each install verified by checking expected files exist
+- [ ] Cross-framework wiring completed (Drive Vector domain)
+- [ ] Momentum scaffold offered if Momentum was installed
+- [ ] Final summary shows all installed frameworks with versions
+- [ ] User informed of next steps
+</acceptance-criteria>

package/modules/mission-control/mission-control/tasks/status.md

@@ -0,0 +1,125 @@
+<purpose>
+Detect all installed Mission Control frameworks, report versions, health, and identify any issues. Provides a single-glance view of what's installed and working.
+</purpose>
+
+<user-story>
+As a Claude Code user, I want to see what frameworks are installed and whether they're healthy, so I know if anything needs attention.
+</user-story>
+
+<when-to-use>
+- Checking what's currently installed in a workspace
+- Verifying an installation completed correctly
+- Diagnosing issues with framework behavior
+- Entry point routes here via /accel status
+</when-to-use>
+
+<context>
+@frameworks/framework-registry.md
+</context>
+
+<steps>
+
+<step name="detect_installed" priority="first">
+Check each framework's installation state.
+
+For each of the 7 frameworks, run detection checks from the registry:
+
+**Vector:**
+- Global install: check `~/.vector/vector.json` exists
+- Hook: check `~/.claude/hooks/vector-hook.py` exists
+- MCP: check `.mcp.json` has `vector-mcp` entry (workspace-level)
+- Version: grep `VECTOR_HOOK_VERSION` from hook file
+
+**Momentum:**
+- Global install: check `~/.claude/momentum-framework/` exists
+- Workspace install: check `.accel/momentum/workspace.json` exists
+- Hooks wired: check `.claude/settings.json` for `.accel/momentum/hooks/` entries
+- MCP: check `.mcp.json` has `momentum-mcp` entry
+- Data surfaces: check `.accel/momentum/data/projects.json` exists
+- Version: read from `.accel/momentum/momentum-mcp/package.json`
+
+**Drive:**
+- Install: check `~/.claude/commands/drive/` exists
+- Framework: check `~/.claude/drive-framework/` exists
+- Version: check package.json or command file headers
+
+**Ignition:**
+- Install: check `~/.claude/commands/ignition/ignition.md` exists
+- Version: read frontmatter from ignition.md
+
+**Forge:**
+- Install: check `~/.claude/commands/forge/forge.md` exists
+- Specs: check `~/.claude/forge-specs/` exists
+- Version: read frontmatter from forge.md
+
+**Radar:**
+- Framework: check `~/.claude/radar/` exists
+- Commands: check `~/.claude/commands/radar/audit.md` exists
+- Tools: check `semgrep --version`, `trivy --version`, `gitleaks --version` etc.
+- Version: grep RADAR_VERSION or count framework files
+
+Run all checks in parallel where possible.
+</step>
+
+<step name="assess_health">
+Evaluate health of installed frameworks.
+
+For each installed framework:
+
+1. **Wiring check**: Is it properly wired? (hooks in settings, MCP in .mcp.json)
+2. **File integrity**: Do expected files exist?
+3. **Staleness**: When was it last modified vs the source repo?
+4. **Cross-framework**: Are expected integrations present? (e.g., Drive domain in Vector)
+
+Health states:
+- **Healthy** — installed, wired, all files present
+- **Degraded** — installed but missing wiring or files
+- **Not installed** — framework not detected
+</step>
+
+<step name="report">
+Present the status report.
+
+Format:
+```
+Mission Control Status
+
+  Framework    Version   Status      Notes
+  ─────────    ───────   ──────      ─────
+  Vector         v2.0.0    Healthy     hook + MCP wired
+  Momentum         v3.0.1    Degraded    hooks not wired (run /momentum:scaffold)
+  Drive         v1.2.0    Healthy     28 commands installed
+  Ignition         v1.0.0    Healthy
+  Forge   v1.0.0    Healthy
+  Radar        v0.2.0    Healthy     10 commands, 3/8 tools installed
+
+  Workspace: {workspace name from .accel/momentum/workspace.json}
+  Drift score: {from .accel/momentum/data/state.json}
+  Last groom: {date}
+
+Issues:
+  - {any degraded items with fix instructions}
+
+Run /accel install {framework} to install missing frameworks.
+Run /accel insights for project-level analytics.
+```
+
+If all healthy, end with: "All frameworks healthy."
+If issues found, list each with the fix command.
+</step>
+
+</steps>
+
+<output>
+Status table showing all 7 frameworks with version, health state, and any issues. Actionable fix instructions for any degraded frameworks.
+</output>
+
+<acceptance-criteria>
+- [ ] All 7 frameworks checked for installation state
+- [ ] Versions detected where possible
+- [ ] Wiring verified (hooks in settings.json, MCPs in .mcp.json)
+- [ ] Health state assigned (Healthy/Degraded/Not installed)
+- [ ] Workspace metadata included (name, drift, groom date)
+- [ ] Issues listed with fix instructions
+- [ ] Output formatted as clean, scannable table
+</acceptance-criteria>

package/modules/mission-control/schemas/entities.schema.json

@@ -0,0 +1,89 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "mission-control/entities.schema.json",
+  "title": "Mission Control Entities",
+  "description": "Graph layer for people and organizations with relational links to projects. Not a CRM — no contact info, just identity and relationships.",
+  "type": "object",
+  "required": ["version", "last_modified", "entities"],
+  "properties": {
+    "version": {
+      "type": "integer",
+      "const": 1
+    },
+    "last_modified": {
+      "type": "string",
+      "format": "date-time"
+    },
+    "entities": {
+      "type": "array",
+      "items": { "$ref": "#/$defs/entity" }
+    }
+  },
+  "$defs": {
+    "entity": {
+      "type": "object",
+      "required": ["id", "name", "type", "created_at", "updated_at"],
+      "properties": {
+        "id": {
+          "type": "string",
+          "description": "Unique identifier. Convention: ENT-NNN",
+          "pattern": "^ENT-\\d{3,}$"
+        },
+        "name": {
+          "type": "string",
+          "description": "Display name"
+        },
+        "type": {
+          "type": "string",
+          "enum": ["person", "organization"],
+          "description": "Entity type — person or organization only"
+        },
+        "role": {
+          "type": ["string", "null"],
+          "description": "Primary role or relationship context (e.g. 'owner', 'client', 'partner', 'contractor', 'team member', 'employer')",
+          "default": null
+        },
+        "relations": {
+          "type": "array",
+          "description": "Links to project items in projects.json",
+          "items": {
+            "type": "object",
+            "required": ["project_id", "relationship"],
+            "properties": {
+              "project_id": {
+                "type": "string",
+                "description": "ID from projects.json (INI-NNN, PRJ-NNN, or TSK-NNN)"
+              },
+              "relationship": {
+                "type": "string",
+                "description": "Nature of relationship (e.g. stakeholder, client, owner, partner, contractor, assignee)"
+              }
+            }
+          },
+          "default": []
+        },
+        "notes": {
+          "type": "array",
+          "description": "Timestamped notes about this entity",
+          "items": {
+            "type": "object",
+            "required": ["text", "timestamp"],
+            "properties": {
+              "text": { "type": "string" },
+              "timestamp": { "type": "string", "format": "date-time" }
+            }
+          },
+          "default": []
+        },
+        "created_at": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "updated_at": {
+          "type": "string",
+          "format": "date-time"
+        }
+      }
+    }
+  }
+}