@nlaprell/shipit 1.0.0

package/.cursor/commands/create_intent_from_issue.md

@@ -0,0 +1,28 @@
+# /create-intent-from-issue
+
+Create a new intent from an existing GitHub issue (fetch title/body, create intent file, set GitHub issue link).
+
+## Usage
+
+```
+/create-intent-from-issue <issue-number>
+```
+
+Example: `/create-intent-from-issue 42`
+
+## What It Does
+
+1. Fetches the issue with `gh issue view <number> --json title,body,number`.
+2. Creates a new intent file under `work/intent/features/` with the next F-XXX ID.
+3. Sets the intent title from the issue title, motivation from the issue body.
+4. Writes `## GitHub issue` with `#<number>` in the new intent file.
+
+## Prerequisites
+
+- `gh` CLI installed and authenticated.
+- `jq` installed (for parsing JSON from gh).
+
+## Instructions
+
+1. Run: `pnpm create-intent-from-issue <issue-number>` (or `./scripts/gh/create-intent-from-issue.sh <issue-number>`).
+2. The script creates e.g. `work/intent/features/F-001.md` with content derived from the issue and links it via the GitHub issue section.

package/.cursor/commands/create_pr.md

@@ -0,0 +1,28 @@
+# /create-pr
+
+Generate a PR summary (if needed) and create a GitHub PR for the current intent.
+
+## Usage
+
+```
+/create-pr <intent-id>
+```
+
+Example: `/create-pr F-001`
+
+## What It Does
+
+1. Ensures `work/workflow-state/pr.md` exists (or `work/workflow-state/<intent-id>/pr.md` for per-intent layout). If missing, the user should run `/pr <intent-id>` first.
+2. Runs `pnpm gh-create-pr <intent-id>` (or `./scripts/gh/create-pr.sh <intent-id>`) to create a GitHub PR with the PR body from that file.
+
+## Prerequisites
+
+- `gh` CLI installed and authenticated.
+- Current branch has commits to push (PR will be created from current branch).
+- Intent has workflow state and `/pr` has been run so pr.md exists.
+
+## Instructions
+
+1. If `work/workflow-state/pr.md` (or `work/workflow-state/<intent-id>/pr.md`) does not exist, run `/pr <intent-id>` first to generate it.
+2. Run: `pnpm gh-create-pr <intent-id>` (or `./scripts/gh/create-pr.sh <intent-id>`).
+3. The script creates the PR with title from the intent and body from pr.md.

package/.cursor/commands/dashboard.md

@@ -0,0 +1,39 @@
+# /dashboard
+
+Start the ShipIt web dashboard.
+
+## Usage
+
+```
+/dashboard
+```
+
+Or from CLI: `pnpm dashboard`
+
+## What It Does
+
+1. Runs `pnpm export-dashboard` to export intents, workflow state, calibration, drift, and doc links to `dashboard-app/public/dashboard.json`
+2. Starts the dashboard dev server (Vite + React)
+3. Opens the dashboard in your browser (or visit the URL shown)
+
+## When to Use
+
+- View intents (planned/active/shipped/killed) at a glance
+- See current phase and active intent
+- Check "waiting for approval" status for human gates
+- View confidence calibration metrics
+- Access documentation links
+- Monitor drift metrics
+
+## Data Source
+
+Read-only. Data is sourced from:
+
+- work/intent/
+- work/workflow-state/
+- \_system/artifacts/ (confidence-calibration.json, usage.json)
+- \_system/drift/metrics.md
+
+## Refresh
+
+The dashboard has a "Refresh" button that reloads the JSON. For fresh data, restart `pnpm dashboard` so the export runs again before the UI loads.

package/.cursor/commands/deploy.md

@@ -0,0 +1,152 @@
+# /deploy
+
+Deploy project to production with automated readiness checks and deployment.
+
+## Usage
+
+```
+/deploy [environment]
+```
+
+Example: `/deploy production`
+
+## What It Does
+
+This command performs production deployment:
+
+1. **Production Readiness Checks:**
+   - All tests pass
+   - Coverage thresholds met
+   - Security audit clean
+   - No high-risk issues
+   - Documentation complete
+   - No blocking drift violations
+
+2. **Deployment Configuration:**
+   - Environment setup
+   - Configuration validation
+   - Secrets management check
+
+3. **Deployment Execution:**
+   - Run deployment scripts
+   - Health checks
+   - Rollback preparation
+
+4. **Post-Deployment:**
+   - Validation
+   - Monitoring setup
+   - Deployment history tracking
+
+## Process
+
+**Switch to Steward role** (read `.cursor/rules/steward.mdc`):
+
+### Step 1: Pre-Deployment Checks
+
+1. **Test Suite:**
+   - Run: `pnpm test` (or equivalent)
+   - Verify all tests pass
+   - Check coverage: `pnpm test:coverage`
+   - Verify coverage >= threshold (from `project.json`)
+
+2. **Code Quality:**
+   - Run: `pnpm lint && pnpm typecheck`
+   - Verify no errors
+   - Check for blocking issues
+
+3. **Security Audit:**
+   - Run: `pnpm audit` (or equivalent)
+   - Check for high/critical vulnerabilities
+   - Verify no secrets in code
+   - Review high-risk domain changes
+
+4. **Documentation:**
+   - Verify README is up to date
+   - Check CHANGELOG has entries
+   - Verify API docs (if applicable)
+   - Check deployment docs exist
+
+5. **Drift Check:**
+   - Run: `pnpm drift-check`
+   - Review drift metrics
+   - Verify no critical drift violations
+
+6. **Invariants:**
+   - Verify `_system/architecture/invariants.yml` is valid
+   - Check no invariant violations
+   - Review architecture canon compliance
+
+### Step 2: Deployment Configuration
+
+1. **Environment Selection:**
+   - Determine target environment (dev/staging/prod)
+   - Load environment-specific config
+   - Validate configuration
+
+2. **Secrets Check:**
+   - Verify required secrets are available
+   - Check secrets are not in code
+   - Validate secret format
+
+3. **Infrastructure:**
+   - Check infrastructure is ready
+   - Verify resources are available
+   - Check quotas/limits
+
+### Step 3: Deployment Execution
+
+1. **Pre-Deployment:**
+   - Create deployment backup
+   - Tag current version
+   - Prepare rollback plan
+
+2. **Deploy:**
+   - Run deployment scripts
+   - Monitor deployment progress
+   - Check for errors
+
+3. **Post-Deployment:**
+   - Run health checks
+   - Verify endpoints are responding
+   - Check logs for errors
+   - Validate functionality
+
+### Step 4: Validation & Tracking
+
+1. **Validation:**
+   - Run smoke tests
+   - Check critical paths
+   - Verify metrics are being collected
+
+2. **Documentation:**
+   - Update deployment history
+   - Record deployment time
+   - Note any issues
+
+3. **Monitoring:**
+   - Verify monitoring is active
+   - Check alerts are configured
+   - Validate dashboards
+
+## Output
+
+Creates:
+
+- Deployment log
+- Deployment history entry
+- Rollback instructions (if needed)
+
+## Rollback
+
+If deployment fails:
+
+1. Run rollback script
+2. Restore previous version
+3. Verify system is stable
+4. Document failure reason
+
+## See Also
+
+- `scripts/deploy.sh` - Deployment script
+- `scripts/check-readiness.sh` - Readiness checks
+- `project.json` - Project settings

package/.cursor/commands/drift_check.md

@@ -0,0 +1,36 @@
+# /drift_check
+
+Calculate and record drift metrics to detect system entropy.
+
+## Usage
+
+```
+/drift_check
+```
+
+## What It Does
+
+Runs the drift metrics script and updates `_system/drift/metrics.md` with:
+
+1. **PR Size Trend** - Average files changed in last 20 PRs
+2. **Test-to-Code Ratio** - Ratio of test lines to code lines
+3. **Dependency Growth** - Count of dependencies and devDependencies
+4. **Untracked New Concepts** - New files without corresponding intents
+5. **CI Performance** - Time-to-green metrics (manual update)
+
+## Output
+
+Updates `_system/drift/metrics.md` with current metrics and compares against baselines in `_system/drift/baselines.md`.
+
+## When to Use
+
+- Weekly automated check (via CI)
+- Before major releases
+- When investigating system entropy
+- After significant refactoring
+
+## See Also
+
+- `scripts/drift-check.sh` - The underlying script
+- `_system/drift/baselines.md` - Baseline thresholds
+- `_system/drift/metrics.md` - Current metrics

package/.cursor/commands/fix.md

@@ -0,0 +1,39 @@
+# /fix
+
+Detect and auto-fix common intent issues.
+
+## Usage
+
+```
+/fix
+```
+
+## What It Does
+
+1. **Scans all intent files** for common issues:
+   - Dependency ordering conflicts (dependency in later release than dependent)
+   - Whitespace formatting issues in dependency lists
+   - Missing dependencies (referenced but don't exist)
+   - Circular dependencies
+
+2. **Shows preview** of all issues found with fix suggestions
+
+3. **Prompts for confirmation** before applying fixes
+
+4. **Auto-fixes** issues where possible:
+   - Normalizes whitespace in dependency lists
+   - Moves dependencies to correct release targets
+   - Flags issues requiring manual intervention (missing deps, circular deps)
+
+## Output
+
+Shows:
+- List of issues found
+- Fix suggestions for each issue
+- Confirmation prompt
+- Summary of fixes applied
+
+## See Also
+
+- `scripts/fix-intents.sh` - Underlying script
+- `scripts/lib/validate-intents.sh` - Validation library

package/.cursor/commands/generate_release_plan.md

@@ -0,0 +1,31 @@
+# /generate-release-plan
+
+Generate a release plan from intents (priorities, dependencies, and status).
+
+## Usage
+
+```
+/generate-release-plan
+```
+
+## What It Does
+
+1. **Reads intents:**
+   - Scans `work/intent/` for intent files
+   - Extracts priority, effort, status, dependencies
+2. **Plans releases:**
+   - Orders intents by dependency and priority
+   - Buckets into releases (R1, R2, R3)
+3. **Writes output:**
+   - Creates `work/release/plan.md`
+   - Lists missing dependencies and exclusions
+
+## Output
+
+Creates:
+
+- `work/release/plan.md` - Ordered release plan with dependencies
+
+## See Also
+
+- `scripts/generate-release-plan.sh` - Underlying script

package/.cursor/commands/generate_roadmap.md

@@ -0,0 +1,38 @@
+# /generate-roadmap
+
+Regenerate roadmap files from current intents.
+
+## Usage
+
+```
+/generate-roadmap
+```
+
+## What To Do
+
+Run this command in the terminal:
+
+```bash
+./scripts/generate-roadmap.sh
+```
+
+Or if `pnpm` scripts are set up:
+
+```bash
+pnpm generate-roadmap
+```
+
+## Output
+
+Updates these files based on intent status and dependencies:
+
+- `work/roadmap/now.md` — Intents with no unmet dependencies (ready to work on)
+- `work/roadmap/next.md` — Intents with dependencies on "Now" items
+- `work/roadmap/later.md` — Intents with deeper dependency chains or lower priority
+- `_system/artifacts/dependencies.md` — Dependency graph visualization
+
+## When To Use
+
+- After creating or modifying intents
+- After changing intent status or dependencies
+- To verify roadmap reflects current state

package/.cursor/commands/help.md

@@ -0,0 +1,37 @@
+# /help
+
+Show context-aware help for ShipIt commands.
+
+## Usage
+
+```
+/help [command]
+```
+
+If no command is specified, shows a list of all available commands.
+
+If a command is specified, shows detailed help for that command.
+
+## Examples
+
+```bash
+/help                    # Show all commands
+/help ship               # Show help for /ship
+/help new_intent         # Show help for /new_intent
+/help generate-roadmap    # Show help for /generate-roadmap
+```
+
+## Available Commands
+
+- `/init-project` - Initialize a new ShipIt project
+- `/scope-project` - AI-assisted feature breakdown
+- `/new_intent` - Create a new intent (interactive wizard)
+- `/ship` - Run full SDLC workflow
+- `/verify` - Re-run verification phase
+- `/kill` - Kill an intent
+- `/generate-release-plan` - Build release plan
+- `/generate-roadmap` - Generate roadmap
+- `/deploy` - Deploy with readiness checks
+- `/drift_check` - Check for entropy
+- `/status` - Show project status
+- `/suggest` - Get suggested next actions

package/.cursor/commands/init_project.md

@@ -0,0 +1,26 @@
+# /init-project
+
+> **⚠️ DEPRECATED for user projects:** This command is deprecated for creating user projects. Use the ShipIt CLI instead:
+>
+> - `create-shipit-app <project-name>` - Create a new ShipIt project
+> - `shipit init` - Attach ShipIt to an existing project
+>
+> **Internal use only:** This command is now only used internally by the framework to create `tests/test-project/` for end-to-end testing.
+
+## Internal Use (Framework Testing)
+
+This command is used internally to create the test project at `tests/test-project/` for ShipIt framework validation.
+
+**Usage (internal only):**
+
+```bash
+./scripts/init-project.sh shipit-test
+```
+
+This creates `tests/test-project/` with test fixtures from `tests/fixtures.json`. The script:
+
+- Only works when run from ShipIt framework repo root
+- Reads test values from `tests/fixtures.json` (no prompts)
+- Creates test project at `tests/test-project/` (fixed location)
+
+**For user projects:** Use `create-shipit-app` or `shipit init` instead.

package/.cursor/commands/kill.md

@@ -0,0 +1,72 @@
+# /kill
+
+Kill an intent with rationale and rollback notes.
+
+## Usage
+
+```
+/kill <intent-id> [reason]
+```
+
+Example: `/kill F-042 "Cannot satisfy latency invariant"`
+
+## What It Does
+
+1. **Marks intent as killed:**
+   - Updates intent file: `status: killed`
+   - Records kill date and reason
+
+2. **Documents rationale:**
+   - Which kill criteria were triggered
+   - Why the intent cannot proceed
+   - What was attempted
+
+3. **Rollback notes:**
+   - What needs to be reverted (if implementation started)
+   - Database migrations to roll back
+   - Feature flags to disable
+
+4. **Updates workflow state:**
+   - Marks `work/workflow-state/active.md` as killed
+   - Archives state files
+
+## Script
+
+Run:
+
+```bash
+./scripts/kill-intent.sh <intent-id> [reason]
+```
+
+## Kill Criteria
+
+An intent is killed when ANY of these trigger:
+
+- Cannot satisfy latency invariant without major redesign
+- Requires breaking schema compatibility beyond allowed versions
+- Adds >20% complexity to core execution path
+- Conflicts with architecture canon
+- Requires >N days without progress
+- Cost exceeds budget by >X%
+
+## Output
+
+Updates the intent file at `work/intent/**/<intent-id>.md` (based on type):
+
+```markdown
+## Status
+
+killed
+
+## Kill Rationale
+
+- Kill criterion: Cannot satisfy latency invariant
+- Reason: [detailed explanation]
+- Date: 2026-01-12
+```
+
+## Who Can Kill
+
+- **Steward:** Can kill any intent
+- **Any agent:** Can propose kill (Steward decides)
+- **Human:** Can override any kill decision

package/.cursor/commands/new_intent.md

@@ -0,0 +1,68 @@
+# /new_intent
+
+Interactive wizard to create a new intent file.
+
+## Usage
+
+```
+/new_intent
+```
+
+This command will guide you through creating a new intent with an interactive wizard.
+
+## Interactive Prompts
+
+The wizard will ask for:
+
+1. **Intent Type** - Feature (F-###), Bug (B-###), or Tech Debt (T-###)
+2. **Template (optional)** - Generic (default), API endpoint, Frontend feature, Infra change, Bugfix, Refactor. Kind-specific templates add sections and prompts (e.g. API: path/method, schema; Bugfix: reproduction, root cause).
+3. **Title** - Short, descriptive title
+4. **Motivation** - Why it exists (1-3 bullets, type 'done' when finished)
+5. **Priority** - p0 (Critical), p1 (High), p2 (Medium), p3 (Low)
+6. **Effort** - Small (s), Medium (m), Large (l)
+7. **Release Target** - R1 (Next), R2 (Following), R3 (Future), R4 (Backlog)
+8. **Dependencies** - Other intent IDs (e.g., F-001, F-002) or 'none'
+9. **Risk Level** - Low, Medium, High
+
+## What It Creates
+
+- New intent file (by type):
+  - Feature: `work/intent/features/<intent-id>.md`
+  - Bug: `work/intent/bugs/<intent-id>.md`
+  - Tech debt: `work/intent/tech-debt/<intent-id>.md`
+- All fields pre-filled based on your inputs
+- Automatically regenerates roadmap files
+- Automatically regenerates release plan
+
+## Example
+
+```bash
+/new_intent
+→ Intent Type: [1] Feature
+→ Title: Add user authentication
+→ Motivation: [Enter bullets, type 'done']
+→ Priority: [2] p1
+→ Effort: [2] Medium
+→ Release Target: [1] R1
+→ Dependencies: F-001, F-002 [or 'none']
+→ Risk Level: [3] High
+
+✓ Intent created successfully!
+  ID: F-003
+  Title: Add user authentication
+  ...
+```
+
+## Next Steps
+
+After creating an intent:
+
+1. Review the generated file
+2. Fill in acceptance criteria, invariants, and other details
+3. Run `/ship <intent-id>` to start the workflow
+
+## Related Commands
+
+- `/ship <id>` - Start working on an intent
+- `/status` - See all intents and their status
+- `/help new_intent` - Detailed help

package/.cursor/commands/pr.md

@@ -0,0 +1,77 @@
+# /pr
+
+Generate a pull request description and checklist for an intent.
+
+## Usage
+
+```
+/pr <intent-id>
+```
+
+Example: `/pr F-042`
+
+## What It Does
+
+Creates a PR-ready summary using the intent and workflow state files.
+
+## Inputs
+
+- `work/intent/**/<intent-id>.md` (commonly `intent/features/<intent-id>.md`)
+- `work/workflow-state/02_plan.md`
+- `work/workflow-state/03_implementation.md`
+- `work/workflow-state/04_verification.md`
+- `work/workflow-state/05_release_notes.md`
+
+## Output
+
+Writes `work/workflow-state/pr.md` with:
+
+- Intent reference
+- Summary of changes
+- Verification results
+- Risk level
+- Rollback notes
+- Checklist
+
+## Instructions
+
+1. Read the intent and workflow-state files listed above.
+2. Summarize the implemented changes (what/why).
+3. Include verification evidence (tests, lint, typecheck, audit).
+4. Call out any deviations from plan.
+5. Write the result to `work/workflow-state/pr.md`.
+
+## Template
+
+```markdown
+# PR: <intent-id> - <title>
+
+## Intent
+
+- <intent-id>: <short description>
+
+## Summary
+
+- Change 1
+- Change 2
+
+## Verification
+
+- `pnpm test` → PASS
+- `pnpm lint && pnpm typecheck` → PASS
+- `pnpm audit --audit-level=high` → PASS
+
+## Risk Level
+
+- low | medium | high
+
+## Rollback
+
+- <rollback steps or reference to work/workflow-state/02_plan.md>
+
+## Checklist
+
+- [ ] Acceptance criteria met
+- [ ] Verification evidence recorded
+- [ ] Rollback plan documented
+```