azclaude-copilot 0.1.3 → 0.1.5

package/README.md

@@ -424,7 +424,7 @@ azclaude-copilot/
 ├── DOCS.md                          <- full user guide
 ├── SECURITY.md                      <- security policy + architecture
 ├── tests/
-│   └── test-features.sh          ← 1039 tests
+│   └── test-features.sh          ← 1048 tests
 ```
 
 ---
@@ -450,11 +450,11 @@ The runner is stateless. These files ARE the state.
 
 ## Verified
 
-1039 tests. Every template, command, capability, agent, and CLI feature verified.
+1048 tests. Every template, command, capability, agent, and CLI feature verified.
 
 ```bash
 bash tests/test-features.sh
-# Results: 1039 passed, 0 failed, 1039 total
+# Results: 1048 passed, 0 failed, 1048 total
 ```
 
 ---

package/bin/copilot.js

@@ -169,7 +169,11 @@ for (let session = 1; session <= maxSessions; session++) {
   console.log(`\n── Session ${session}/${maxSessions} ${elapsed > 0 ? `(${elapsed}min elapsed)` : ''} ──`);
 
   // Build state-aware prompt
-  let prompt = 'You are in AZCLAUDE Copilot mode. Run /copilot to continue autonomous building.';
+  // IMPORTANT: In -p mode, slash commands (/setup, /copilot) don't work.
+  // Tell Claude to read and follow the command .md files directly.
+  let prompt = 'You are in AZCLAUDE Copilot mode. You are running in non-interactive mode (-p flag).';
+  prompt += '\n\nIMPORTANT: Slash commands like /setup do NOT work in -p mode. Instead, read the command file and follow its instructions. For example, to run /copilot: read .claude/commands/copilot.md and follow it. To run /setup: read .claude/commands/setup.md and follow it.';
+  prompt += '\n\nRead .claude/commands/copilot.md now and follow it to continue autonomous building.';
   prompt += `\n\nOriginal intent: ${intent}`;
   prompt += `\n\nSession ${session}/${maxSessions}.`;
 
@@ -184,13 +188,13 @@ for (let session = 1; session <= maxSessions; session++) {
       const total = statuses.length;
       prompt += `\n\nPlan progress: ${done}/${total} done, ${blocked} blocked, ${pending} remaining.`;
       if (blocked > 0) prompt += ' Check blockers.md — retry blocked milestones if new context helps.';
-      if (done > 0 && done % 3 === 0) prompt += ' 3+ milestones since last /evolve — run /reflexes analyze + /evolve.';
-      if (pending === 0 && blocked === 0) prompt += ' All milestones done — run /audit then /ship.';
+      if (done > 0 && done % 3 === 0) prompt += ' 3+ milestones since last /evolve — read .claude/commands/reflexes.md then .claude/commands/evolve.md.';
+      if (pending === 0 && blocked === 0) prompt += ' All milestones done — read .claude/commands/audit.md then .claude/commands/ship.md.';
     } else {
       prompt += '\n\nPlan exists but plan.md not found. Read .claude/plan.md for status.';
     }
   } else {
-    prompt += '\n\nNo plan yet. Start with /setup then /blueprint to create milestones.';
+    prompt += '\n\nNo plan yet. Read .claude/commands/setup.md and follow it, then read .claude/commands/blueprint.md to create milestones.';
   }
 
   // Run Claude Code session

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "azclaude-copilot",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Autonomous product builder. Describe once, AZCLAUDE builds it across sessions — planning, implementing, testing, evolving, deploying. Zero human input.",
   "bin": {
     "azclaude": "./bin/cli.js",

package/templates/commands/evolve.md

@@ -150,7 +150,37 @@ If the file doesn't exist, create it with this header:
 
 ---
 
-## Step 7: Promote GENERAL Skills
+## Step 7: Generate Project-Specific Skills and Agents from Evidence
+
+### Skills from git evidence
+```bash
+git log --name-only --format="" --diff-filter=AM | sort | uniq -c | sort -rn | head -20
+```
+If a file pattern appears 5+ times (e.g., `src/components/*.tsx`, `content/*.md`, `api/routes/*.py`):
+1. Read `.claude/capabilities/level-builders/level3-skills.md`
+2. Create a skill that encodes the workflow for that pattern
+3. Save to `.claude/commands/{skill-name}.md`
+4. Only create if no existing skill covers this workflow
+
+### Agents from co-change clusters
+```bash
+git log --name-only --format="" --diff-filter=M | sort | uniq -c | sort -rn | head -30
+```
+If 3+ files in the same directory change together across 3+ commits:
+1. Read `.claude/capabilities/level-builders/level5-agents.md`
+2. Create an agent with all 5 layers in `.claude/agents/cc-{name}.md`
+3. Use co-change data for scope boundaries
+4. Only create if no existing agent covers this cluster
+
+### Check existing before creating
+```bash
+ls .claude/commands/*.md .claude/agents/*.md 2>/dev/null
+```
+Skip creation if a skill/agent already covers the same workflow.
+
+---
+
+## Step 8: Promote GENERAL Skills
 
 For any fix tagged GENERAL in EVALUATE:
 1. Copy to `~/shared-skills/{name}.md`

package/templates/commands/setup.md

@@ -70,7 +70,49 @@ The orchestrator-init agent:
 
 ---
 
-## Step 5: Quality Gate
+## Step 5: Generate Project-Specific Skills
+
+Read `.claude/capabilities/level-builders/level3-skills.md` for the skill design guide.
+
+Analyze the project's domain, stack, and recurring workflows:
+1. Check what file types and patterns exist (endpoints, pages, components, schemas, tests)
+2. Check git log for repeated commit patterns (what work is done most often)
+3. Identify 2-4 project-specific skills that would encode the most common workflows
+
+For each skill:
+- Create `.claude/commands/{skill-name}.md` with pushy description (3+ trigger variants)
+- Follow RECIPE pattern (steps to do something, not documentation)
+- Include completion rule
+- ≤ 500 lines (references/ subdir for overflow)
+
+**Stack-specific defaults** (generate if stack detected):
+| Stack | Generate |
+|-------|---------|
+| Next.js / React | `new-page.md`, `new-component.md` |
+| Express / FastAPI | `new-endpoint.md` |
+| Any DB | `migrate.md` |
+| Any deploy config | `deploy.md` |
+| Markdown content | `new-content.md`, `validate-content.md` |
+| Exam / quiz | `new-exam.md`, `validate-exam.md` |
+
+**TaskUpdate → completed** for Create skills.
+
+---
+
+## Step 6: Generate Project-Specific Agents (if project has 10+ files)
+
+Read `.claude/capabilities/level-builders/level5-agents.md` for agent design guide.
+
+1. Run co-change analysis: `git log --name-only --format="" --diff-filter=M | sort | uniq -c | sort -rn | head -30`
+2. Identify file clusters that change independently → each cluster = potential agent
+3. Create 1-3 agents in `.claude/agents/cc-{name}.md` with all 5 layers
+4. Prefix all agents with `cc-` to avoid framework collisions
+
+Skip if project has < 10 files or < 5 commits.
+
+---
+
+## Step 7: Quality Gate
 
 Load `capabilities/shared/quality-check.md` and run the full environment check.