azclaude-copilot 0.4.0 → 0.4.1

package/README.md

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "azclaude-copilot",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "AI coding environment — 26 commands, 8 skills, 10 agents, memory, reflexes, evolution. Install once, works on any stack.",
   "bin": {
     "azclaude": "./bin/cli.js",

package/templates/commands/blueprint.md

@@ -104,7 +104,33 @@ When running inside `/copilot` (detected by: `.claude/copilot-intent.md` exists)
 - Include `Files:` with expected paths
 - Include `Commit:` with conventional commit format
 - Write `## Summary` with counts at the bottom
-- After writing plan.md, return control to /copilot
+
+### Problem-Architect Validation (if available)
+
+After writing plan.md, check:
+```bash
+ls .claude/agents/problem-architect.md 2>/dev/null
+```
+
+If problem-architect.md exists — spawn it for EACH milestone in plan.md:
+```
+Analyze this milestone for the Team Spec:
+Milestone: {description from plan.md}
+Current state: {what files exist in the project}
+Available agents: {list of .claude/agents/}
+Available skills: {list of .claude/skills/}
+```
+
+For each milestone, append the returned Team Spec fields directly into plan.md:
+- `Complexity:` SIMPLE / MEDIUM / COMPLEX
+- `Files Written:` exact paths the builder will touch (critical for parallel safety)
+- `Pre-conditions:` checklist before starting
+- `Risks:` and mitigation
+- `Structural Decision:` YES/NO (if YES → orchestrator must /debate before dispatching)
+
+This pre-annotation makes orchestrator dispatch faster and prevents parallel file collision.
+
+After all milestones annotated — return control to /copilot.
 
 ---
 

package/templates/commands/evolve.md

@@ -203,6 +203,26 @@ ls .claude/commands/*.md .claude/agents/*.md .claude/skills/*/SKILL.md 2>/dev/nu
 Skip creation if a skill/agent already covers the same workflow.
 Update existing ones if they're missing steps discovered in recent sessions.
 
+### 7e: Orchestrator re-evaluation (if intelligent copilot installed)
+
+After generating new agents/skills, check:
+```bash
+ls .claude/agents/orchestrator.md .claude/plan.md 2>/dev/null
+```
+
+If BOTH exist — spawn orchestrator with:
+```
+Re-evaluate plan.md after /evolve created new agents and skills.
+Focus on: which blocked milestones can now be unblocked?
+New agents available: {list of newly created agents}
+New skills available: {list of newly created skills}
+Check blockers.md for each blocked milestone — does a new agent cover the missing capability?
+Update plan.md status for any milestone that is now unblockable (blocked → pending).
+Report: milestones unblocked + reason.
+```
+
+This closes the loop: /evolve creates capability → orchestrator immediately re-routes blocked work.
+
 ---
 
 ## Step 8: Promote GENERAL Skills

package/templates/commands/setup.md

@@ -121,6 +121,27 @@ Read `.claude/capabilities/level-builders/level5-agents.md` for agent design gui
 
 Skip if project has < 10 files or < 5 commits.
 
+### Problem-Architect Supplement (new projects with zero git history)
+
+If the project has < 5 commits (no co-change data), check:
+```bash
+ls .claude/agents/problem-architect.md 2>/dev/null
+```
+
+If problem-architect.md exists — spawn it to analyze the project structure directly:
+```
+Analyze this project to recommend agents and skills.
+No git history available — use file structure and stack signals instead.
+Project stack: {from env-scan.sh output}
+Files found: {top-level structure}
+Domain: {from CLAUDE.md}
+Available agents already installed: {list .claude/agents/}
+Return: recommended cc- agents (with directory claims) + skills to generate
+```
+
+Use the returned recommendations as the basis for agent/skill generation.
+This fills the gap when git history is too thin for co-change analysis.
+
 ---
 
 ## Step 7: Quality Gate