pi-crew 0.2.3 → 0.2.5

package/teams/research.team.md

@@ -1,11 +1,11 @@
----
-name: research
-description: Team for investigation and documentation
-defaultWorkflow: research
-workspaceMode: single
-maxConcurrency: 2
----
-
-- explorer: agent=explorer gather codebase facts
-- analyst: agent=analyst analyze findings
-- writer: agent=writer produce final notes
+---
+name: research
+description: Team for investigation and documentation
+defaultWorkflow: research
+workspaceMode: single
+maxConcurrency: 2
+---
+
+- explorer: agent=explorer gather codebase facts
+- analyst: agent=analyst analyze findings
+- writer: agent=writer produce final notes

package/teams/review.team.md

@@ -1,12 +1,12 @@
----
-name: review
-description: Team for code review and security review
-defaultWorkflow: review
-workspaceMode: single
-maxConcurrency: 2
----
-
-- explorer: agent=explorer understand changed areas
-- reviewer: agent=reviewer review correctness and maintainability
-- security-reviewer: agent=security-reviewer review security risks
-- verifier: agent=verifier summarize pass/fail
+---
+name: review
+description: Team for code review and security review
+defaultWorkflow: review
+workspaceMode: single
+maxConcurrency: 2
+---
+
+- explorer: agent=explorer understand changed areas
+- reviewer: agent=reviewer review correctness and maintainability
+- security-reviewer: agent=security-reviewer review security risks
+- verifier: agent=verifier summarize pass/fail

package/tsconfig.json

@@ -1,19 +1,19 @@
-{
-  "compilerOptions": {
-    "target": "ES2022",
-    "module": "NodeNext",
-    "moduleResolution": "NodeNext",
-    "strict": true,
-    "noImplicitAny": true,
-    "exactOptionalPropertyTypes": false,
-    "skipLibCheck": true,
-    "allowImportingTsExtensions": true,
-    "noEmit": true,
-    "types": ["node"]
-  },
-  "include": [
-    "*.ts",
-    "src/**/*.ts",
-    "test/**/*.ts"
-  ]
-}
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
+    "strict": true,
+    "noImplicitAny": true,
+    "exactOptionalPropertyTypes": false,
+    "skipLibCheck": true,
+    "allowImportingTsExtensions": true,
+    "noEmit": true,
+    "types": ["node"]
+  },
+  "include": [
+    "*.ts",
+    "src/**/*.ts",
+    "test/**/*.ts"
+  ]
+}

package/workflows/default.workflow.md

@@ -1,30 +1,30 @@
----
-name: default
-description: Explore, plan, execute, and verify
----
-
-## explore
-role: explorer
-
-Explore the codebase for the goal: {goal}
-
-## plan
-role: planner
-dependsOn: explore
-output: plan.md
-
-Create a concise implementation plan for: {goal}
-
-## execute
-role: executor
-dependsOn: plan
-
-Implement the plan for: {goal}
-
-## verify
-role: verifier
-dependsOn: execute
-verify: true
-
-Verify completion for: {goal}
-Run tests ONCE (cache to .crew/cache/), read changed files from executor context. Cross-reference test output with the changes. Do NOT re-run tests. Give PASS or FAIL with specific test evidence.
+---
+name: default
+description: Explore, plan, execute, and verify
+---
+
+## explore
+role: explorer
+
+Explore the codebase for the goal: {goal}
+
+## plan
+role: planner
+dependsOn: explore
+output: plan.md
+
+Create a concise implementation plan for: {goal}
+
+## execute
+role: executor
+dependsOn: plan
+
+Implement the plan for: {goal}
+
+## verify
+role: verifier
+dependsOn: execute
+verify: true
+
+Verify completion for: {goal}
+Run tests ONCE (cache to .crew/cache/), read changed files from executor context. Cross-reference test output with the changes. Do NOT re-run tests. Give PASS or FAIL with specific test evidence.

package/workflows/fast-fix.workflow.md

@@ -1,23 +1,23 @@
----
-name: fast-fix
-description: Minimal workflow for small fixes
----
-
-## explore
-role: explorer
-
-Find the likely source of the issue: {goal}
-
-## execute
-role: executor
-dependsOn: explore
-
-Make the smallest safe fix.
-
-## verify
-role: verifier
-dependsOn: execute
-verify: true
-
-Verify the fix with available evidence.
-Run tests ONCE (cache to .crew/cache/), read changed files from executor context. Cross-reference test output with the fix. Do NOT re-run tests. Give PASS or FAIL with specific test evidence.
+---
+name: fast-fix
+description: Minimal workflow for small fixes
+---
+
+## explore
+role: explorer
+
+Find the likely source of the issue: {goal}
+
+## execute
+role: executor
+dependsOn: explore
+
+Make the smallest safe fix.
+
+## verify
+role: verifier
+dependsOn: execute
+verify: true
+
+Verify the fix with available evidence.
+Run tests ONCE (cache to .crew/cache/), read changed files from executor context. Cross-reference test output with the fix. Do NOT re-run tests. Give PASS or FAIL with specific test evidence.

package/workflows/implementation.workflow.md

@@ -1,43 +1,43 @@
----
-name: implementation
-description: Adaptive implementation workflow where a planner agent decides the subagent fanout
----
-
-## assess
-role: planner
-output: adaptive-plan.json
-
-Assess this task and decide how many subagents are actually needed for: {goal}
-
-You are the orchestration planner. Inspect the repository enough to choose an efficient crew; do not use a fixed template. Small/simple tasks may need one executor plus one verifier. Risky or broad tasks may need parallel explorers, specialists, implementers, reviewers, security reviewers, or test engineers.
-
-Return a concise rationale, then include exactly one JSON block between these markers:
-
-ADAPTIVE_PLAN_JSON_START
-{
-  "phases": [
-    {
-      "name": "short-phase-name",
-      "tasks": [
-        {
-          "role": "explorer|analyst|planner|critic|executor|reviewer|security-reviewer|test-engineer|verifier|writer",
-          "title": "short task title",
-          "task": "specific autonomous task prompt for this subagent"
-        }
-      ]
-    }
-  ]
-}
-ADAPTIVE_PLAN_JSON_END
-
-Rules:
-- **MAXIMIZE PARALLELISM**: Put independent tasks in the SAME phase so they run concurrently.
-  For example, if a task needs exploration + implementation + review, use 3 phases:
-  Phase 1: explorers (2-3 in parallel), Phase 2: executors (2-3 in parallel), Phase 3: reviewers (2 in parallel).
-  NEVER create sequential phases when tasks are independent.
-- Choose the smallest effective number of subagents per phase.
-- Tasks within the same phase run in parallel; phases run sequentially.
-- Include verification/review tasks when implementation is requested.
-- Do not include more than 12 total subagents; split or summarize oversized plans instead.
-- A good plan for a complex task has 2-4 phases with 2-4 parallel tasks each.
-- A simple task may have just 1-2 phases with 1-2 tasks.
+---
+name: implementation
+description: Adaptive implementation workflow where a planner agent decides the subagent fanout
+---
+
+## assess
+role: planner
+output: adaptive-plan.json
+
+Assess this task and decide how many subagents are actually needed for: {goal}
+
+You are the orchestration planner. Inspect the repository enough to choose an efficient crew; do not use a fixed template. Small/simple tasks may need one executor plus one verifier. Risky or broad tasks may need parallel explorers, specialists, implementers, reviewers, security reviewers, or test engineers.
+
+Return a concise rationale, then include exactly one JSON block between these markers:
+
+ADAPTIVE_PLAN_JSON_START
+{
+  "phases": [
+    {
+      "name": "short-phase-name",
+      "tasks": [
+        {
+          "role": "explorer|analyst|planner|critic|executor|reviewer|security-reviewer|test-engineer|verifier|writer",
+          "title": "short task title",
+          "task": "specific autonomous task prompt for this subagent"
+        }
+      ]
+    }
+  ]
+}
+ADAPTIVE_PLAN_JSON_END
+
+Rules:
+- **MAXIMIZE PARALLELISM**: Put independent tasks in the SAME phase so they run concurrently.
+  For example, if a task needs exploration + implementation + review, use 3 phases:
+  Phase 1: explorers (2-3 in parallel), Phase 2: executors (2-3 in parallel), Phase 3: reviewers (2 in parallel).
+  NEVER create sequential phases when tasks are independent.
+- Choose the smallest effective number of subagents per phase.
+- Tasks within the same phase run in parallel; phases run sequentially.
+- Include verification/review tasks when implementation is requested.
+- Do not include more than 12 total subagents; split or summarize oversized plans instead.
+- A good plan for a complex task has 2-4 phases with 2-4 parallel tasks each.
+- A simple task may have just 1-2 phases with 1-2 tasks.

package/workflows/parallel-research.workflow.md

@@ -1,46 +1,46 @@
----
-name: parallel-research
-description: Parallel research with shard exploration and synthesis
----
-
-## discover
-role: explorer
-
-Discover the relevant files/projects for: {goal}. Return a shard plan with paths grouped by topic. Do not deeply read every file yet; focus on routing the work.
-
-## explore-core
-role: explorer
-parallelGroup: explore
-
-Explore the core/runtime shard from the discover output. Focus on architecture, package config, docs, and reusable patterns for: {goal}
-
-## explore-ui
-role: explorer
-parallelGroup: explore
-
-Explore the UI/TUI/extension-interface shard from the discover output. Focus on widgets, overlays, commands, status bars, package config, docs, and reusable patterns for: {goal}
-
-## explore-runtime
-role: explorer
-parallelGroup: explore
-
-Explore the worker/runtime/subagent/runtime-control shard from the discover output. Focus on process/session/runtime orchestration, event streams, logs, package config, docs, and reusable patterns for: {goal}
-
-## explore-extensions
-role: explorer
-parallelGroup: explore
-
-Explore the extension bundle/small-package shard from the discover output. Focus on package config, extension registration, commands/tools, docs, and reusable patterns for: {goal}
-
-## synthesize
-role: analyst
-dependsOn: explore-core, explore-ui, explore-runtime, explore-extensions
-
-Synthesize all shard findings. Use discover output if available, but do not require it. Identify common patterns, gaps, and concrete recommendations.
-
-## write
-role: writer
-dependsOn: synthesize
-output: research-summary.md
-
-Write a concise final summary with evidence, risks, and actionable next steps.
+---
+name: parallel-research
+description: Parallel research with shard exploration and synthesis
+---
+
+## discover
+role: explorer
+
+Discover the relevant files/projects for: {goal}. Return a shard plan with paths grouped by topic. Do not deeply read every file yet; focus on routing the work.
+
+## explore-core
+role: explorer
+parallelGroup: explore
+
+Explore the core/runtime shard from the discover output. Focus on architecture, package config, docs, and reusable patterns for: {goal}
+
+## explore-ui
+role: explorer
+parallelGroup: explore
+
+Explore the UI/TUI/extension-interface shard from the discover output. Focus on widgets, overlays, commands, status bars, package config, docs, and reusable patterns for: {goal}
+
+## explore-runtime
+role: explorer
+parallelGroup: explore
+
+Explore the worker/runtime/subagent/runtime-control shard from the discover output. Focus on process/session/runtime orchestration, event streams, logs, package config, docs, and reusable patterns for: {goal}
+
+## explore-extensions
+role: explorer
+parallelGroup: explore
+
+Explore the extension bundle/small-package shard from the discover output. Focus on package config, extension registration, commands/tools, docs, and reusable patterns for: {goal}
+
+## synthesize
+role: analyst
+dependsOn: explore-core, explore-ui, explore-runtime, explore-extensions
+
+Synthesize all shard findings. Use discover output if available, but do not require it. Identify common patterns, gaps, and concrete recommendations.
+
+## write
+role: writer
+dependsOn: synthesize
+output: research-summary.md
+
+Write a concise final summary with evidence, risks, and actionable next steps.

package/workflows/research.workflow.md

@@ -1,22 +1,22 @@
----
-name: research
-description: Research and write up findings
----
-
-## explore
-role: explorer
-
-Gather relevant facts for: {goal}
-
-## analyze
-role: analyst
-dependsOn: explore
-
-Analyze and organize the findings.
-
-## write
-role: writer
-dependsOn: analyze
-output: research-summary.md
-
-Write a concise final summary with evidence and open questions.
+---
+name: research
+description: Research and write up findings
+---
+
+## explore
+role: explorer
+
+Gather relevant facts for: {goal}
+
+## analyze
+role: analyst
+dependsOn: explore
+
+Analyze and organize the findings.
+
+## write
+role: writer
+dependsOn: analyze
+output: research-summary.md
+
+Write a concise final summary with evidence and open questions.

package/workflows/review.workflow.md

@@ -1,30 +1,30 @@
----
-name: review
-description: Review workflow for correctness and security
----
-
-## explore
-role: explorer
-
-Identify changed or relevant areas for review: {goal}
-
-## code-review
-role: reviewer
-dependsOn: explore
-parallelGroup: review
-
-Review correctness, maintainability, tests, and regressions.
-
-## security-review
-role: security-reviewer
-dependsOn: explore
-parallelGroup: review
-
-Review security risks and trust boundaries.
-
-## verify
-role: verifier
-dependsOn: code-review, security-review
-verify: true
-
-Run the project test suite ONCE (cache to .crew/cache/), then cross-reference test results with reviewer and security-reviewer findings. Confirm each finding against real test output. Give PASS if findings match evidence, FAIL if critical findings are false positives or tests reveal new issues.
+---
+name: review
+description: Review workflow for correctness and security
+---
+
+## explore
+role: explorer
+
+Identify changed or relevant areas for review: {goal}
+
+## code-review
+role: reviewer
+dependsOn: explore
+parallelGroup: review
+
+Review correctness, maintainability, tests, and regressions.
+
+## security-review
+role: security-reviewer
+dependsOn: explore
+parallelGroup: review
+
+Review security risks and trust boundaries.
+
+## verify
+role: verifier
+dependsOn: code-review, security-review
+verify: true
+
+Run the project test suite ONCE (cache to .crew/cache/), then cross-reference test results with reviewer and security-reviewer findings. Confirm each finding against real test output. Give PASS if findings match evidence, FAIL if critical findings are false positives or tests reveal new issues.

package/skills/task-packet/SKILL.md

@@ -1,28 +0,0 @@
----
-name: task-packet
-description: Structured worker task-packet template. Use when creating or executing worker tasks that need clear objective, scope, constraints, outputs, acceptance criteria, and verification.
----
-
-# task-packet
-
-Use this skill when creating or executing a worker task.
-
-## Required sections
-
-Each task should clarify:
-
-- objective;
-- scope and paths;
-- constraints and permissions;
-- dependencies and expected inputs;
-- expected outputs/artifacts;
-- acceptance criteria;
-- verification commands;
-- escalation conditions.
-
-## Worker behavior
-
-- Read dependency outputs before starting dependent work.
-- Keep outputs concise and artifact-oriented.
-- Do not claim completion until required artifacts and status are durable.
-- If blocked, report the blocker and the smallest recoverable next action.

package/skills/verify-evidence/SKILL.md

@@ -1,27 +0,0 @@
----
-name: verify-evidence
-description: Final verification evidence checklist. Use before finalizing implementation, review, or audit work to report changed files, checks run, artifacts, risks, and rollback notes.
----
-
-# verify-evidence
-
-Use this skill before finalizing implementation, review, or audit work.
-
-## Required final evidence
-
-Include:
-
-- changed files, or `none` for read-only work;
-- tests/checks run with pass/fail result;
-- relevant artifacts, run IDs, or log paths;
-- unresolved risks and rollback notes when code changed.
-
-## Verification ladder
-
-Prefer the smallest reliable check first, then escalate:
-
-1. Targeted unit tests for touched behavior.
-2. Typecheck for TypeScript changes.
-3. Integration tests for runtime/spawn/state changes.
-4. `npm pack --dry-run` for package/release/doc changes.
-5. Real Pi smoke only when needed and safe.