@soleri/forge 9.0.0 → 9.0.1

package/src/skills/context-resume.md

@@ -1,146 +0,0 @@
----
-name: context-resume
-description: Use when starting a new session, returning to work, or when the user asks "what was I working on", "where did I leave off", "catch me up", "morning standup", "resume", "what's the status". Reconstructs full working context from memory, plans, and sessions.
----
-
-# Context Resume — Pick Up Where You Left Off
-
-Reconstruct your full working context in seconds. Chains memory, plans, sessions, and brain to rebuild exactly where you left off — even across session boundaries and context compactions.
-
-## When to Use
-
-- Starting a new Claude Code session
-- Returning after a break
-- "What was I working on?"
-- "Morning standup"
-- After context compaction (session_capture fires automatically, this reads it back)
-
-## The Magic: Full Context Reconstruction
-
-### Step 1: Load Active Plans
-
-Check for plans in progress — these are your active work streams:
-
-```
-YOUR_AGENT_core op:plan_stats
-```
-
-For each active plan, load its details and task status:
-
-```
-YOUR_AGENT_core op:get_plan
-YOUR_AGENT_core op:plan_list_tasks
-  params: { planId: "<id>" }
-```
-
-Present:
-
-- Plan objective and current status
-- Which tasks are completed, in progress, or pending
-- What's next to do
-
-### Step 2: Search Recent Memory
-
-Load the latest session summaries — these capture what happened before:
-
-```
-YOUR_AGENT_core op:memory_search
-  params: { query: "session summary" }
-```
-
-```
-YOUR_AGENT_core op:memory_list
-```
-
-Also check recent vault captures — what knowledge was added recently?
-
-```
-YOUR_AGENT_core op:vault_recent
-```
-
-### Step 3: Check Active Loops
-
-See if there's a validation loop in progress:
-
-```
-YOUR_AGENT_core op:loop_is_active
-```
-
-If active:
-
-```
-YOUR_AGENT_core op:loop_status
-```
-
-This tells you if an iterative workflow (TDD, debugging, migration) was mid-flight.
-
-### Step 4: Brain Snapshot
-
-Get the latest brain insights relevant to current work:
-
-```
-YOUR_AGENT_core op:brain_strengths
-```
-
-### Step 5: System Health
-
-Quick health check to make sure everything is working:
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-## Presenting the Resume
-
-Format as a concise standup:
-
-```
-## Where You Left Off
-
-**Active Plans:**
-- [Plan name] — X/Y tasks complete, next: [task description]
-
-**Last Session:**
-- [Summary from memory — what was done, key decisions]
-
-**Recent Captures:**
-- [New patterns/anti-patterns added to vault]
-
-**Active Loops:**
-- [Any in-progress validation loops]
-
-**Brain Says:**
-- [Top relevant patterns for current work]
-
-**Health:** [OK / Issues found]
-
-## Recommended Next Step
-[Based on active plans and last session context]
-```
-
-## The Magic
-
-This feels like magic because the user just says "catch me up" and the agent:
-
-1. Knows what plans are active and where they stand
-2. Remembers what happened last session (even across context compactions)
-3. Shows what knowledge was recently captured
-4. Detects in-flight loops
-5. Recommends what to work on next
-
-No other tool does this — the agent has genuine persistent memory.
-
-## Agent Tools Reference
-
-| Op                | When to Use                 |
-| ----------------- | --------------------------- |
-| `plan_stats`      | Find active plans           |
-| `get_plan`        | Load plan details           |
-| `plan_list_tasks` | See task status within plan |
-| `memory_search`   | Find session summaries      |
-| `memory_list`     | Browse recent memories      |
-| `vault_recent`    | Recently captured knowledge |
-| `loop_is_active`  | Check for in-flight loops   |
-| `loop_status`     | Get loop details            |
-| `brain_strengths` | Relevant proven patterns    |
-| `admin_health`    | System health check         |

package/src/skills/deliver-and-ship.md

@@ -1,123 +0,0 @@
----
-name: deliver-and-ship
-description: >
-  Use when the user says "ship it", "ready to deploy", "package", "release",
-  "pre-PR check", "delivery checklist", "is this ready", "final review", or mentions
-  shipping, deploying, packaging, or releasing work. Runs pre-delivery quality gates
-  to ensure nothing ships without passing stability, knowledge capture, and code quality checks.
----
-
-# Deliver & Ship — Quality Gate Runner
-
-Run all pre-delivery quality gates before shipping. This ensures nothing leaves without passing stability checks, knowledge capture, and code quality verification.
-
-## When to Use
-
-When work is considered "done" and ready to be committed, PR'd, or deployed. This is the last checkpoint before code leaves the developer's hands.
-
-## Orchestration Sequence
-
-### Step 1: Code Quality
-
-Run the project's linter, formatter, and type checker on all modified files:
-
-1. Check for lint/format scripts in `package.json` (or equivalent)
-2. Run `typecheck` / `tsc --noEmit` if TypeScript
-3. Run any project-specific quality gates (clippy for Rust, mypy for Python, etc.)
-
-Any type error or lint failure is a blocker.
-
-### Step 2: Test Suite
-
-Run the full test suite to catch regressions:
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-Verify the agent itself is healthy, then run project tests. All tests must pass.
-
-### Step 3: Stability Assessment
-
-Classify the changes as safe or breaking:
-
-- **Safe**: Internal refactors, bug fixes, additive features (new exports, new ops)
-- **Breaking**: Removed exports, changed signatures, renamed public APIs, schema migrations
-- Breaking changes need migration guidance in the commit/PR description
-
-### Step 4: Knowledge Audit
-
-Check if patterns discovered during this work session should be captured before shipping:
-
-```
-YOUR_AGENT_core op:memory_search
-  params: { query: "current session" }
-```
-
-```
-YOUR_AGENT_core op:brain_stats
-```
-
-Look for:
-
-- Bug fixes that reveal an anti-pattern worth capturing
-- New patterns that should be in the vault for next time
-- Architectural decisions that need documenting
-
-Uncaptured knowledge is lost knowledge. If something should be captured:
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<what was learned>",
-    description: "<the pattern or anti-pattern>",
-    type: "pattern",
-    tags: ["<relevant-tags>"]
-  }
-```
-
-### Step 5: Commit Quality
-
-Verify commit messages follow conventional commits:
-
-- `feat:` for new features
-- `fix:` for bug fixes
-- `refactor:` for refactors
-- `chore:` for maintenance
-- No AI attribution (blocked by engine rules)
-
-### Step 6: Delivery Report
-
-Present a checklist:
-
-- [ ] Code quality: pass/fail (Step 1)
-- [ ] Tests: pass/fail (Step 2)
-- [ ] Stability: safe change / breaking change (Step 3)
-- [ ] Knowledge: captured / needs capture (Step 4)
-- [ ] Commits: clean / needs cleanup (Step 5)
-
-All items must pass before recommending "ship it."
-
-## Domain-Specific Gates
-
-Agents with domain-specific facades may add extra gates. For example:
-
-- **Design system agents**: token validation, contrast checks, accessibility audit
-- **API agents**: schema validation, backward compatibility checks
-- **Security agents**: dependency audit, secret scanning
-
-These are additive — they don't replace the generic gates above.
-
-## Exit Criteria
-
-Delivery is approved when all gates pass. If any gate fails, report the failure and recommend fixes before shipping. Never approve delivery with blocking issues.
-
-## Agent Tools Reference
-
-| Op | When to Use |
-|----|-------------|
-| `admin_health` | Verify agent/system health |
-| `memory_search` | Check for uncaptured session knowledge |
-| `brain_stats` | Review learning state |
-| `capture_knowledge` | Persist patterns before shipping |
-| `capture_quick` | Fast capture for simple learnings |

package/src/skills/env-setup.md

@@ -1,151 +0,0 @@
----
-name: env-setup
-description: >
-  Use when a developer needs to set up, fix, or restore a local development environment.
-  Triggers on post-clone setup, project onboarding, first-time running a repo, pulled changes
-  that broke the build, missing or misconfigured dependencies, MODULE_NOT_FOUND or Cannot find
-  module errors, gyp ERR or native module build failures, missing .env files or unknown required
-  environment variables, database setup, Docker compose issues, or connection refused during
-  local dev. Covers Node.js, Python, Rust, Go, Ruby, PHP, and Docker-based projects.
----
-
-# Environment Setup
-
-Detect what a project needs, diagnose what's missing, and produce an actionable setup checklist.
-
-## Overview
-
-Scan the project root for configuration files, detect the tech stack and dependencies, identify gaps between what's required and what's present, then generate ordered setup steps. Offer to execute each step.
-
-## When to Use
-
-- Just cloned a repo and need to get it running
-- Getting errors after pulling changes (missing deps, env vars, DB migrations)
-- Onboarding to an unfamiliar project
-- Setting up a project on a new machine
-- Docker/container environment not starting
-- Missing `.env` file or environment variables
-
-## Detection Phase
-
-Scan the project root and identify:
-
-### Package Managers & Dependencies
-
-| File | Stack | Install Command |
-|------|-------|-----------------|
-| `package.json` | Node.js | `npm install` / `yarn` / `pnpm install` (check for lockfile) |
-| `requirements.txt` | Python | `pip install -r requirements.txt` |
-| `pyproject.toml` | Python | `pip install -e .` or `poetry install` or `uv sync` |
-| `Pipfile` | Python | `pipenv install` |
-| `Cargo.toml` | Rust | `cargo build` |
-| `go.mod` | Go | `go mod download` |
-| `Gemfile` | Ruby | `bundle install` |
-| `composer.json` | PHP | `composer install` |
-
-**Lockfile priority:** If a lockfile exists (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `Pipfile.lock`, `poetry.lock`), use the matching package manager. Don't mix.
-
-### Environment Variables
-
-1. Check for `.env.example`, `.env.sample`, `.env.template`
-2. Check for existing `.env` — if missing, copy from template
-3. Parse template for required variables (lines without defaults or with placeholder values)
-4. Flag variables that need real values (API keys, secrets, database URLs)
-5. **If no template exists:** grep source for `process.env.`, `os.environ`, `env::var`, `os.Getenv` to discover env vars the project actually uses.
-
-### Native Dependencies
-
-| Indicator | What It Means |
-|-----------|--------------|
-| `better-sqlite3`, `sqlite3` in deps | Needs C++ compiler |
-| `node-gyp` in deps or scripts | Needs Python 3 + C++ toolchain |
-| `sharp` in deps | Needs `libvips` |
-| `Cargo.toml` with `[build-dependencies]` | Needs Rust toolchain for build scripts |
-| `setup.py` with `ext_modules` | Needs C compiler for Python extensions |
-
-### Databases
-
-| File/Config | Database | Setup Needed |
-|-------------|----------|-------------|
-| `docker-compose.yml` with postgres/mysql | PostgreSQL/MySQL | Container + migrations |
-| `prisma/schema.prisma` | Prisma-managed | `npx prisma migrate dev` |
-| `drizzle.config.*` | Drizzle-managed | `npx drizzle-kit push` |
-| `alembic.ini` | SQLAlchemy | `alembic upgrade head` |
-| `config/database.yml` | Rails | `rails db:create db:migrate` |
-
-### Infrastructure
-
-| File | What It Means |
-|------|--------------|
-| `docker-compose.yml` | Services to start with `docker compose up` |
-| `Dockerfile` | Can build container locally |
-| `Makefile` | Check for `setup`, `install`, `dev` targets |
-| `.tool-versions` / `.node-version` / `.nvmrc` | Required runtime version |
-| `turbo.json` / `nx.json` / `lerna.json` | Monorepo setup |
-
-### IDE & Tool Integration
-
-| File | Integration |
-|------|------------|
-| `.vscode/` | VS Code settings, extensions |
-| `.mcp.json` / `mcp.json` | MCP server config |
-| `.editorconfig` | Cross-editor formatting |
-
-## Diagnosis Phase
-
-After detection, check what's present vs needed:
-
-1. **Runtime version** — does installed version match version files?
-2. **Dependencies installed?** — does `node_modules/`, `venv/`, `vendor/` exist?
-3. **Native build tools?** — are compilers available?
-4. **Env file present?** — does `.env` exist when a template does?
-5. **Database reachable?** — can the configured DB URL connect?
-6. **Docker running?** — is Docker daemon running if needed?
-7. **Build artifacts** — does the project need an initial build step?
-
-## Checklist Generation
-
-Produce steps in dependency order:
-
-```
-## Setup Checklist
-
-1. [ ] Install runtime (Node 20.x via nvm)
-2. [ ] Install dependencies (pnpm install)
-3. [ ] Copy environment file (cp .env.example .env)
-4. [ ] Fill in required env vars: DATABASE_URL, API_KEY
-5. [ ] Start Docker services (docker compose up -d)
-6. [ ] Run database migrations (npx prisma migrate dev)
-7. [ ] Build the project (pnpm build)
-8. [ ] Start dev server (pnpm dev)
-```
-
-**Order matters:** runtime → deps → env → infrastructure → migrations → build → run.
-
-After presenting the checklist, offer: "Want me to run these steps for you?"
-
-## Execution Phase
-
-If the user says yes, execute steps sequentially. Stop and ask if:
-
-- A step fails
-- A step requires manual input (API keys, passwords)
-- A step would modify system-level config (global installs, PATH changes)
-
-## Monorepo Handling
-
-If monorepo detected (turbo.json, nx.json, pnpm-workspace.yaml):
-
-1. Install root dependencies first
-2. Ask which package/app the user wants to work on
-3. Check for package-specific setup
-4. Run package-specific setup after root
-
-## Common Mistakes
-
-- **Wrong package manager** — using `npm install` when `yarn.lock` exists. Always check lockfiles first.
-- **Skipping env file** — project crashes on first API call. Always check for templates.
-- **Missing native build tools** — `npm install` fails with gyp errors. Check before installing.
-- **Missing runtime version** — subtle bugs from wrong Node/Python version.
-- **Docker not running** — cryptic "connection refused" errors.
-- **Stale dependencies** — after `git pull`, always re-install if lockfile changed.

package/src/skills/executing-plans.md

@@ -1,216 +0,0 @@
----
-name: executing-plans
-description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
----
-
-<!-- Adapted from superpowers (MIT License) -->
-
-# Executing Plans
-
-## Overview
-
-Load plan, review critically, execute tasks in batches, report for review between batches.
-
-**Core principle:** Batch execution with checkpoints for architect review.
-
-**Announce at start:** "I'm using the executing-plans skill to implement this plan."
-
-## The Process
-
-### Step 1: Load and Review Plan
-
-First, load the tracked plan from the agent:
-
-```
-YOUR_AGENT_core op:get_plan
-```
-
-List all tasks to understand scope:
-
-```
-YOUR_AGENT_core op:plan_list_tasks
-  params: { planId: "<id>" }
-```
-
-Check plan stats for an overview:
-
-```
-YOUR_AGENT_core op:plan_stats
-```
-
-If no tracked plan exists, read the plan file from `docs/plans/`.
-
-Review critically — identify any questions or concerns about the plan.
-
-- If concerns: Raise them with your human partner before starting
-- If no concerns: Create TodoWrite and proceed
-
-### Step 2: Start Execution Loop
-
-For iterative tasks, start a validation loop:
-
-```
-YOUR_AGENT_core op:loop_start
-  params: { prompt: "<plan objective>", mode: "custom" }
-```
-
-The loop tracks iterations and validates progress automatically.
-
-### Step 3: Execute Batch
-
-**Default: First 3 tasks**
-
-For each task:
-
-1. Mark as in_progress:
-   ```
-   YOUR_AGENT_core op:update_task
-     params: { planId: "<id>", taskIndex: <n>, status: "in_progress" }
-   ```
-2. Follow each step exactly (plan has bite-sized steps)
-3. Run verifications as specified
-4. Mark as completed:
-   ```
-   YOUR_AGENT_core op:update_task
-     params: { planId: "<id>", taskIndex: <n>, status: "completed" }
-   ```
-
-After each task, iterate the loop:
-
-```
-YOUR_AGENT_core op:loop_iterate
-```
-
-### Step 4: Report
-
-When batch complete:
-
-- Show what was implemented
-- Show verification output
-- Check loop status:
-  ```
-  YOUR_AGENT_core op:loop_status
-  ```
-- Say: "Ready for feedback."
-
-### Step 5: Continue
-
-Based on feedback:
-
-- Apply changes if needed
-- Execute next batch
-- Repeat until complete
-
-### Step 6: Complete Development
-
-After all tasks complete and verified:
-
-1. Run final verification (use verification-before-completion skill)
-
-2. Complete the validation loop:
-
-   ```
-   YOUR_AGENT_core op:loop_complete
-   ```
-
-3. Reconcile plan — compare what was planned vs what actually happened:
-
-   ```
-   YOUR_AGENT_core op:plan_reconcile
-     params: {
-       planId: "<id>",
-       actualSteps: "<description of what was actually done>",
-       driftNotes: "<what differed from the plan>"
-     }
-   ```
-
-4. Complete plan lifecycle — extract knowledge and archive:
-
-   ```
-   YOUR_AGENT_core op:plan_complete_lifecycle
-     params: { planId: "<id>" }
-   ```
-
-5. Archive the plan for historical reference:
-
-   ```
-   YOUR_AGENT_core op:plan_archive
-     params: { planId: "<id>" }
-   ```
-
-6. Capture a session summary:
-   ```
-   YOUR_AGENT_core op:session_capture
-     params: { summary: "<what was built, key decisions, files modified>" }
-   ```
-
-## Capture Learnings During Execution
-
-If you discover something worth remembering during execution (a gotcha, a better approach, an anti-pattern):
-
-```
-YOUR_AGENT_core op:capture_quick
-  params: {
-    title: "<what you learned>",
-    description: "<context, why it matters, when it applies>"
-  }
-```
-
-Don't wait until the end — capture insights as they happen.
-
-## When to Stop and Ask for Help
-
-**STOP executing immediately when:**
-
-- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
-- Plan has critical gaps preventing starting
-- You don't understand an instruction
-- Verification fails repeatedly
-
-**Ask for clarification rather than guessing.**
-
-## When to Revisit Earlier Steps
-
-**Return to Review (Step 1) when:**
-
-- Partner updates the plan based on your feedback
-- Fundamental approach needs rethinking
-
-**Don't force through blockers** - stop and ask.
-
-## Remember
-
-- Review plan critically first
-- Follow plan steps exactly
-- Don't skip verifications
-- Between batches: just report and wait
-- Stop when blocked, don't guess
-- Capture learnings as you go, not just at the end
-- Always reconcile the plan after execution — drift data makes future plans better
-- Never start implementation on main/master branch without explicit user consent
-
-## Agent Tools Reference
-
-| Op                        | When to Use                                   |
-| ------------------------- | --------------------------------------------- |
-| `get_plan`                | Load tracked plan                             |
-| `plan_list_tasks`         | List all tasks in the plan                    |
-| `plan_stats`              | Plan overview and metrics                     |
-| `update_task`             | Mark tasks in_progress / completed            |
-| `loop_start`              | Begin validation loop for iterative execution |
-| `loop_iterate`            | Track each iteration                          |
-| `loop_status`             | Check loop progress                           |
-| `loop_complete`           | Finish validation loop                        |
-| `plan_reconcile`          | Compare planned vs actual (post-execution)    |
-| `plan_complete_lifecycle` | Extract knowledge from execution              |
-| `plan_archive`            | Archive plan for history                      |
-| `session_capture`         | Save session context                          |
-| `capture_quick`           | Capture mid-execution learnings               |
-
-## Integration
-
-**Required workflow skills:**
-
-- writing-plans — Creates the plan this skill executes
-- verification-before-completion — Verify work before claiming completion
-- test-driven-development — Follow TDD for each implementation step