@bradtaylorsf/alpha-loop 1.1.0 → 1.1.1

package/README.md

@@ -28,24 +28,17 @@ npx @bradtaylorsf/alpha-loop
 ## Quick Start
 
 ```bash
-# 1. Initialize config in your project
+# 1. Initialize — runs full onboarding (config, vision, scan, sync)
 cd your-project
 alpha-loop init
 
-# 2. Edit .alpha-loop.yaml with your repo settings
+# 2. Edit .alpha-loop.yaml if needed (repo, harnesses, model, etc.)
 
-# 3. Set up project vision (optional but recommended)
-alpha-loop vision
-
-# 4. Generate project context
-alpha-loop scan
-
-# 5. Run the loop — you'll be prompted to pick a milestone
+# 3. Run the loop — you'll be prompted to pick a milestone
 alpha-loop run
 
 # Or target a specific milestone directly
 alpha-loop run --milestone "v1.0"
-
 ```
 
 ## How It Works
@@ -127,10 +120,10 @@ During live verification, the agent takes screenshots at key states and saves th
 
 | Command | Description |
 |---------|-------------|
-| `alpha-loop init` | Create `.alpha-loop.yaml` config and install agent skills/templates |
+| `alpha-loop init` | Full onboarding: config, templates, vision, scan, sync, commit |
 | `alpha-loop run` | Fetch matching issues, process them all, then exit |
 | `alpha-loop run --dry-run` | Preview without making changes |
-| `alpha-loop scan` | Generate/refresh project context (`.alpha-loop/context.md`) |
+| `alpha-loop scan` | Generate/refresh project context and instructions file |
 | `alpha-loop vision` | Interactive project vision setup (`.alpha-loop/vision.md`) |
 | `alpha-loop auth` | Save authenticated browser state for verification |
 | `alpha-loop history` | View session history |
@@ -176,6 +169,11 @@ dev_command: pnpm dev
 port: 3000
 auto_merge: true
 
+# Coding harnesses to sync skills/agents to
+harnesses:
+  - claude-code
+  - codex
+
 # Safety limits (0 = unlimited)
 max_issues: 20
 max_session_duration: 7200  # 2 hours in seconds

package/dist/cli.js

@@ -8,7 +8,7 @@ import { syncCommand } from './commands/sync.js';
 program
     .name('alpha-loop')
     .description('Agent-agnostic automated development loop')
-    .version('1.1.0');
+    .version('1.1.1');
 program
     .command('init')
     .description('Full project onboarding: config, templates, vision, scan, sync')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bradtaylorsf/alpha-loop",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Agent-agnostic automated development loop: Plan → Build → Test → Review → Ship",
   "type": "module",
   "packageManager": "pnpm@9.0.0",

package/templates/agents/reviewer.md

@@ -3,7 +3,7 @@ name: reviewer
 description: Reviews code changes, fixes issues found, and produces a review summary. Runs after implementation.
 tools: Read, Write, Edit, Glob, Grep, Bash
 model: opus
-skills: code-review, security-analysis, testing-patterns, test-robustness, api-patterns
+skills: code-review, security-analysis, testing-patterns, test-robustness, api-patterns, docs-sync
 ---
 
 # Reviewer Agent

package/templates/skills/docs-sync/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: docs-sync
+description: Ensure documentation stays in sync with code changes. Trigger when modifying CLI commands, config options, directory structure, or public APIs.
+when-to-use: When adding, removing, or changing CLI commands, config fields, directory layout, or user-facing behavior
+---
+
+# Documentation Sync
+
+When making changes that affect user-facing behavior, always update the corresponding documentation.
+
+## What to check
+
+### CLI commands changed?
+- Update `README.md` commands table
+- Update `CLAUDE.md` commands section
+- Update `--help` descriptions in `src/cli.ts`
+
+### Config options changed?
+- Update `README.md` Configuration Reference table
+- Update `README.md` config example block
+- Update `CLAUDE.md` if it references config
+- Update the config template in `src/commands/init.ts`
+
+### Directory structure changed?
+- Update `CLAUDE.md` Directory Structure section
+- Update `README.md` Project Artifacts table
+
+### New skill or agent added?
+- Skill: create `templates/skills/<name>/SKILL.md` with frontmatter
+- Agent: create `templates/agents/<name>.md` with frontmatter
+- Run `alpha-loop sync` to distribute
+
+### Public API or behavior changed?
+- Update relevant README sections
+- Update CLAUDE.md if architectural
+
+## Rules
+
+- Documentation updates MUST be in the same commit as the code change
+- Never leave README or CLAUDE.md referencing commands, options, or paths that no longer exist
+- When removing a feature, search docs for all references before committing
+- Keep README under 300 lines, CLAUDE.md under 200 lines