@davidorex/pi-project-workflows 0.2.0 → 0.3.1

package/skills/pi-behavior-monitors/references/bundled-resources.md

@@ -0,0 +1,29 @@
+# Bundled Resources
+
+## schemas/ (2 files)
+
+- `schemas/monitor-pattern.schema.json`
+- `schemas/monitor.schema.json`
+
+## examples/ (20 files)
+
+- `examples/commit-hygiene/classify.md`
+- `examples/commit-hygiene.instructions.json`
+- `examples/commit-hygiene.monitor.json`
+- `examples/commit-hygiene.patterns.json`
+- `examples/fragility/classify.md`
+- `examples/fragility.instructions.json`
+- `examples/fragility.monitor.json`
+- `examples/fragility.patterns.json`
+- `examples/hedge/classify.md`
+- `examples/hedge.instructions.json`
+- `examples/hedge.monitor.json`
+- `examples/hedge.patterns.json`
+- `examples/unauthorized-action/classify.md`
+- `examples/unauthorized-action.instructions.json`
+- `examples/unauthorized-action.monitor.json`
+- `examples/unauthorized-action.patterns.json`
+- `examples/work-quality/classify.md`
+- `examples/work-quality.instructions.json`
+- `examples/work-quality.monitor.json`
+- `examples/work-quality.patterns.json`

package/skills/pi-project/SKILL.md

@@ -0,0 +1,231 @@
+---
+name: pi-project
+description: >
+  Schema-driven project state management with typed JSON blocks, schema
+  validation, planning lifecycle, and cross-block referential integrity. Use when
+  managing .project/ blocks, scaffolding project structure, validating project
+  state, or adding work items.
+---
+
+<tools_reference>
+<tool name="append-block-item">
+Append an item to an array in a project block file. Schema validation is automatic.
+
+*Append items to project blocks (gaps, decisions, or any user-defined block)*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `block` | string | yes | Block name (e.g., 'gaps', 'decisions') |
+| `arrayKey` | string | yes | Array key in the block (e.g., 'gaps', 'decisions') |
+| `item` | unknown | yes | Item object to append — must conform to block schema |
+</tool>
+
+<tool name="update-block-item">
+Update fields on an item in a project block array. Finds by predicate field match.
+
+*Update items in project blocks — change status, add details, mark resolved*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `block` | string | yes | Block name (e.g., 'gaps', 'decisions') |
+| `arrayKey` | string | yes | Array key in the block |
+| `match` | object | yes | Fields to match (e.g., { id: 'gap-123' }) |
+| `updates` | object | yes | Fields to update (e.g., { status: 'resolved' }) |
+</tool>
+
+<tool name="read-block">
+Read a project block file as structured JSON.
+
+*Read a project block as structured JSON*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `block` | string | yes | Block name (e.g., 'gaps', 'tasks', 'requirements') |
+</tool>
+
+<tool name="write-block">
+Write or replace an entire project block with schema validation.
+
+*Write or replace a project block with schema validation*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `block` | string | yes | Block name (e.g., 'project', 'architecture') |
+| `data` | unknown | yes | Complete block data — must conform to block schema |
+</tool>
+
+<tool name="project-status">
+Get derived project state — source metrics, block summaries, planning lifecycle status.
+
+*Get project state — source metrics, block summaries, planning lifecycle status*
+
+</tool>
+
+<tool name="project-validate">
+Validate cross-block referential integrity — check that IDs referenced across blocks exist.
+
+*Validate cross-block referential integrity*
+
+</tool>
+
+<tool name="project-init">
+Initialize .project/ directory with default schemas and empty block files.
+
+*Initialize .project/ directory with default schemas and blocks*
+
+</tool>
+
+</tools_reference>
+
+<commands_reference>
+<command name="/project">
+Project state management
+
+Subcommands: `init`, `status`, `add-work`, `validate`
+</command>
+
+</commands_reference>
+
+<events>
+`session_start`
+</events>
+
+<bundled_resources>
+22 defaults bundled.
+See references/bundled-resources.md for full inventory.
+</bundled_resources>
+
+<planning_vocabulary>
+
+**Block Types:**
+
+| Block | Title | Array Key | Item Fields |
+|-------|-------|-----------|-------------|
+| `architecture` | Architecture | `modules` | name, file, responsibility, dependencies? (array), lines? (integer) |
+| `audit` | audit | `checks` | id, description, status (string (pass|fail|warn|skip)), category?, details? |
+| `conformance-reference` | conformance-reference | `principles` | id, name, description?, rules (array) |
+| `decisions` | Decisions | `decisions` | id, decision, rationale, phase? (string|integer), status (string (decided|tentative|revisit|superseded)), context? |
+| `domain` | Domain Knowledge | `entries` | id, title, content, category (string (research|reference|domain-rule|prior-art|constraint)), source?, confidence? (string (high|medium|low)), related_requirements? (array), tags? (array) |
+| `gaps` | Gaps | `gaps` | id, description, status (string (open|resolved|deferred)), category (string (missing|incomplete|defect|improvement|technical-debt|question)), priority (string (low|medium|high|critical)), phase? (string|integer), resolved_by?, source? (string (human|agent|monitor|workflow)), details? |
+| `handoff` | Handoff | `current_tasks` |  |
+| `phase` | Phase | `success_criteria` | criterion, verify_method (string (command|inspect|test)) |
+| `project` | Project Identity | `target_users` |  |
+| `rationale` | Design Rationale | `rationales` | id, title, narrative, related_decisions? (array), phase? (string|integer), context? |
+| `requirements` | Requirements | `requirements` | id, description, type (string (functional|non-functional|constraint|integration)), status (string (proposed|accepted|deferred|implemented|verified)), priority (string (must|should|could|wont)), acceptance_criteria? (array), source? (string (human|agent|analysis)), traces_to? (array), depends_on? (array) |
+| `tasks` | Tasks | `tasks` | id, description, status (string (planned|in-progress|completed|blocked|cancelled)), phase? (string|integer), files? (array), acceptance_criteria? (array), depends_on? (array), assigned_agent?, verification?, notes? |
+| `verification` | Verification | `verifications` | id, target, target_type (string (task|phase|requirement)), status (string (passed|failed|partial|skipped)), method (string (command|inspect|test)), evidence?, timestamp?, criteria_results? (array) |
+
+**Status Enums:**
+
+| Block | Field | Values |
+|-------|-------|--------|
+| `audit` | `status` | pass, fail, warn, skip |
+| `audit` | `severity` | error, warning, info |
+| `decisions` | `status` | decided, tentative, revisit, superseded |
+| `domain` | `category` | research, reference, domain-rule, prior-art, constraint |
+| `domain` | `confidence` | high, medium, low |
+| `gaps` | `status` | open, resolved, deferred |
+| `gaps` | `category` | missing, incomplete, defect, improvement, technical-debt, question |
+| `gaps` | `priority` | low, medium, high, critical |
+| `gaps` | `source` | human, agent, monitor, workflow |
+| `phase` | `status` | planned, in-progress, completed |
+| `phase` | `verify_method` | command, inspect, test |
+| `phase` | `status` | planned, in-progress, completed |
+| `project` | `status` | inception, planning, development, maintenance, complete |
+| `requirements` | `type` | functional, non-functional, constraint, integration |
+| `requirements` | `status` | proposed, accepted, deferred, implemented, verified |
+| `requirements` | `priority` | must, should, could, wont |
+| `requirements` | `source` | human, agent, analysis |
+| `tasks` | `status` | planned, in-progress, completed, blocked, cancelled |
+| `verification` | `target_type` | task, phase, requirement |
+| `verification` | `status` | passed, failed, partial, skipped |
+| `verification` | `method` | command, inspect, test |
+
+</planning_vocabulary>
+
+<objective>
+pi-project manages structured project state in `.project/` — a directory of JSON block files validated against schemas.
+</objective>
+
+<block_files>
+Blocks are JSON files in `.project/` (e.g., `gaps.json`, `decisions.json`). Each block has a corresponding schema in `.project/schemas/`. When you write to a block via the tools, the data is validated against its schema before persisting. Writes are atomic (tmp file + rename).
+</block_files>
+
+<schema_validation>
+Every block write validates against `.project/schemas/<blockname>.schema.json`. If the schema file doesn't exist, writes proceed without validation. Validation errors include the specific JSON Schema violations.
+</schema_validation>
+
+<project_init>
+`/project init` scaffolds the `.project/` directory with default schemas and empty block files from the package's `defaults/` directory. Idempotent — skips files that already exist.
+</project_init>
+
+<project_status>
+`/project status` derives project state dynamically from the filesystem:
+- Source file count and line count (`.ts` files excluding tests)
+- Test count and test file count
+- Schema count, block count, phase count
+- Block summaries with array item counts and status distributions
+- Requirements summary (total, by status, by priority) — from requirements.json
+- Tasks summary (total, by status) — from tasks.json
+- Domain entry count — from domain.json
+- Verification summary (total, passed, failed) — from verification.json
+- Handoff presence — whether handoff.json exists
+- Recent git commits
+- Current phase detection
+</project_status>
+
+<project_add_work>
+`/project add-work` discovers appendable blocks (blocks with array schemas), reads their schemas, and sends a structured instruction to the LLM to extract items from the conversation into the typed blocks. This is a follow-up message that triggers the LLM to use the `append-block-item` tool.
+</project_add_work>
+
+<duplicate_detection>
+`append-block-item` checks for duplicate items by `id` field before appending. If an item with the same `id` already exists in the target array, it returns a message instead of appending.
+</duplicate_detection>
+
+<project_validate>
+`/project validate` checks cross-block referential integrity:
+- task.phase references a valid phase
+- task.depends_on references valid task IDs
+- decision.phase references a valid phase
+- gap.resolved_by references a valid ID
+- requirement.traces_to references valid phase/task IDs
+- requirement.depends_on references valid requirement IDs
+- verification.target references a valid target ID
+- rationale.related_decisions references valid decision IDs
+
+Returns errors (broken dependency references) and warnings (unresolved cross-references).
+</project_validate>
+
+<planning_lifecycle>
+The default schemas support a full planning lifecycle:
+- **project.json** — identity, vision, goals, constraints, scope, status
+- **domain.json** — research findings, reference material, domain rules
+- **requirements.json** — functional/non-functional requirements with MoSCoW priority and lifecycle states
+- **architecture.json** — modules, patterns, boundaries
+- **phases/** — ordered delivery units with goals, success criteria, inputs/outputs
+- **tasks.json** — standalone task registry with status lifecycle and phase linkage
+- **decisions.json** — choices with rationale and phase association
+- **gaps.json** — open items with priority, category, and resolution tracking
+- **rationale.json** — design rationale with decision cross-references
+- **handoff.json** — session context snapshot (created on-demand, not by /project init)
+- **verification.json** — completion evidence per task/phase/requirement
+- **conformance-reference.json** — executable code conventions with principles, rules, check methods (grep/command/ast/inspect), and check patterns. Ships empty, populated per-project by agents or users.
+- **audit** (schema only, no default block) — structured audit results produced by running conformance checks.
+
+All schemas are user-customizable. Edit `.project/schemas/*.schema.json` to add fields, change enums, or restructure blocks without modifying code.
+</planning_lifecycle>
+
+<update_check>
+On `session_start`, checks npm registry for newer versions of `@davidorex/pi-project-workflows` and notifies via UI if an update is available. Non-blocking — failures are silently ignored.
+</update_check>
+
+<success_criteria>
+- `.project/` directory exists with schemas and block files after `/project init`
+- Block writes validate against schemas — invalid data rejected with specific error
+- `/project status` returns current derived state without errors
+- `/project validate` returns no errors for well-formed cross-block references
+- `append-block-item` rejects duplicate IDs
+- Schema customizations (field additions, enum changes) take effect on next write
+</success_criteria>
+
+*Generated from source by `scripts/generate-skills.js` — do not edit by hand.*

package/skills/pi-project/references/bundled-resources.md

@@ -0,0 +1,26 @@
+# Bundled Resources
+
+## defaults/ (22 files)
+
+- `defaults/blocks/conformance-reference.json`
+- `defaults/blocks/decisions.json`
+- `defaults/blocks/domain.json`
+- `defaults/blocks/gaps.json`
+- `defaults/blocks/project.json`
+- `defaults/blocks/rationale.json`
+- `defaults/blocks/requirements.json`
+- `defaults/blocks/tasks.json`
+- `defaults/blocks/verification.json`
+- `defaults/schemas/architecture.schema.json`
+- `defaults/schemas/audit.schema.json`
+- `defaults/schemas/conformance-reference.schema.json`
+- `defaults/schemas/decisions.schema.json`
+- `defaults/schemas/domain.schema.json`
+- `defaults/schemas/gaps.schema.json`
+- `defaults/schemas/handoff.schema.json`
+- `defaults/schemas/phase.schema.json`
+- `defaults/schemas/project.schema.json`
+- `defaults/schemas/rationale.schema.json`
+- `defaults/schemas/requirements.schema.json`
+- `defaults/schemas/tasks.schema.json`
+- `defaults/schemas/verification.schema.json`

package/skills/pi-project-workflows/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: pi-project-workflows
+description: >
+  Meta-package re-exporting pi-project (schema-driven project state),
+  pi-workflows (workflow orchestration), and pi-behavior-monitors (autonomous
+  behavior monitoring). Install once to get all three extensions.
+---
+
+<objective>
+This meta-package re-exports all three extensions. Install once to get everything:
+
+```
+pi install npm:@davidorex/pi-project-workflows
+```
+</objective>
+
+<included_extensions>
+<extension name="@davidorex/pi-project">
+Schema-driven project state management for Pi
+
+**Tools:** `append-block-item`, `update-block-item`, `read-block`, `write-block`, `project-status`, `project-validate`, `project-init`
+**Commands:** `/project`
+</extension>
+
+<extension name="@davidorex/pi-workflows">
+Workflow orchestration extension for Pi
+
+**Tools:** `workflow`, `workflow-list`, `workflow-agents`, `workflow-validate`, `workflow-status`, `workflow-init`
+**Commands:** `/workflow`
+**Shortcuts:** ctrl+h (Pause running workflow), ctrl+j (Resume paused workflow)
+</extension>
+
+<extension name="@davidorex/pi-behavior-monitors">
+Behavior monitors for pi that watch agent activity and steer corrections
+
+**Tools:** `monitors-status`, `monitors-inspect`, `monitors-control`, `monitors-rules`, `monitors-patterns`
+**Commands:** `/monitors`
+</extension>
+
+</included_extensions>
+
+*Generated from source by `scripts/generate-skills.js` — do not edit by hand.*

package/skills/pi-workflows/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: pi-workflows
+description: >
+  Orchestrates multi-step agent workflows defined in YAML with DAG-based
+  execution, typed data flow, checkpoint/resume, and output validation. Use when
+  running workflows, authoring workflow specs, debugging step failures, or
+  inspecting agent configurations.
+---
+
+<tools_reference>
+<tool name="workflow">
+Run a named workflow with typed input. Discovers workflows from .workflows/ and ~/.pi/agent/workflows/.
+
+*Run a multi-step workflow with typed data flow between agents*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `workflow` | string | yes | Name of the workflow to run |
+| `input` | unknown | no | Input data for the workflow (validated against workflow's input schema) |
+| `fresh` | string | no | Set to 'true' to start a fresh run, ignoring any incomplete prior runs |
+</tool>
+
+<tool name="workflow-list">
+List available workflows with names, descriptions, and sources.
+
+*List available workflows with names, descriptions, and sources*
+
+</tool>
+
+<tool name="workflow-agents">
+List available agents with full specs, or inspect a single agent by name. Returns role, description, model, tools, output format/schema, prompt template paths.
+
+*List available agents with specs, or inspect a single agent by name*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `name` | string | no | Agent name to inspect (omit to list all) |
+</tool>
+
+<tool name="workflow-validate">
+Validate workflow specs — check agents, schemas, step references, and filters.
+
+*Validate workflow specs — check agents, schemas, step references, filters*
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `name` | string | no | Workflow name to validate (omit to validate all) |
+</tool>
+
+<tool name="workflow-status">
+Get workflow vocabulary — step types, filters, available agents, workflows, schemas, templates.
+
+*Get workflow vocabulary — step types, filters, available agents, workflows, schemas*
+
+</tool>
+
+<tool name="workflow-init">
+Initialize .workflows/ directory for workflow run state.
+
+*Initialize .workflows/ directory for workflow run state*
+
+</tool>
+
+</tools_reference>
+
+<commands_reference>
+<command name="/workflow">
+List and run workflows
+
+Subcommands: `init`, `run`, `list`, `resume`, `validate`, `status`
+</command>
+
+</commands_reference>
+
+<keyboard_shortcuts>
+- **ctrl+h** — Pause running workflow
+- **ctrl+j** — Resume paused workflow
+</keyboard_shortcuts>
+
+<bundled_resources>
+21 agents, 11 schemas, 14 workflows, 28 templates bundled.
+See references/bundled-resources.md for full inventory.
+</bundled_resources>
+
+<objective>
+pi-workflows orchestrates multi-step agent workflows defined in YAML. Workflows are DAGs of typed steps with data flow via `${{ }}` expressions.
+</objective>
+
+<workflow_discovery>
+Workflows are discovered from three locations (first match wins):
+1. `.workflows/*.workflow.yaml` — project-level
+2. `~/.pi/agent/workflows/*.workflow.yaml` — user-level
+3. Package bundled `workflows/` — built-in
+</workflow_discovery>
+
+<step_types>
+| Type | Field | Description |
+|------|-------|-------------|
+| agent | `agent: name` | Dispatch an LLM subprocess via `pi --mode json` |
+| command | `command: "..."` | Run a shell command, capture stdout as output |
+| monitor | `monitor: name` | Run a monitor classification as a verification gate |
+| transform | `transform: { mapping: {...} }` | Pure data transformation via expressions, no LLM |
+| gate | `gate: { check: "..." }` | Shell command exit code as pass/fail boolean |
+| loop | `loop: { maxAttempts, steps }` | Repeat sub-steps until gate breaks or max reached |
+| parallel | `parallel: { a: ..., b: ... }` | Run named sub-steps concurrently |
+| pause | `pause: true` or `pause: "message"` | Pause execution, resumable later |
+| forEach | `forEach: "${{ expr }}"` | Iterate over an array, executing the step per element |
+</step_types>
+
+<expression_syntax>
+`${{ expression }}` resolves against scope: `input`, `steps`, `loop`, `forEach`.
+
+Access step outputs: `${{ steps.investigate.output.findings }}`
+Filters: `${{ steps.analyze.output | json }}`, `${{ items | length }}`, `${{ name | upper }}`
+
+Available filters: length, keys, filter, json, upper, lower, trim, default, first, last, join, split, replace, includes, map, sum, min, max, sort, unique, flatten, zip, group_by, count_by, chunk, pick, omit, entries, from_entries, merge, values, not, and, or.
+</expression_syntax>
+
+<agent_resolution>
+Agent specs (`.agent.yaml`) are resolved from three locations (first match wins):
+1. `.pi/agents/<name>.agent.yaml` — project-level
+2. `~/.pi/agent/agents/<name>.agent.yaml` — user-level
+3. Package bundled `agents/<name>.agent.yaml` — built-in
+
+Agent specs define: model, thinking level, tools, system prompt (or template), task template, output format/schema.
+</agent_resolution>
+
+<execution_model>
+1. Steps are ordered by YAML declaration order
+2. DAG planner infers parallelism from `${{ steps.X }}` references
+3. Steps without explicit dependencies run after their predecessor (conservative sequential)
+4. Each step's result is persisted atomically to `<runDir>/state.json`
+5. TUI progress widget shows real-time step status, cost, and timing
+</execution_model>
+
+<checkpoint_resume>
+Incomplete runs (failed or paused) are detected on next invocation. If the workflow spec hasn't changed incompatibly, execution resumes from the last completed step. Failed steps are re-executed. Use `fresh: "true"` to force a new run.
+</checkpoint_resume>
+
+<output_validation>
+Steps with `output.schema` validate the agent's JSON output against a JSON Schema file. Validation failure marks the step as failed.
+
+Use `block:<name>` to reference project block schemas portably: `output.schema: block:project` resolves to `.project/schemas/project.schema.json` from cwd. Works across monorepo, npm install, and user-customized schemas. Combined with `retry: { maxAttempts: 2 }`, the agent gets the schema validation error injected into its retry prompt and can self-correct.
+</output_validation>
+
+<retry>
+Steps with `retry: { maxAttempts: N }` are re-executed on failure. Between retries:
+- Project block files are rolled back to pre-attempt state
+- Prior error messages are injected into the prompt
+- Optional `steeringMessage` provides custom retry guidance
+</retry>
+
+<completion_messages>
+After execution, the workflow result is injected into the main LLM conversation. The `completion` field controls this: either a `template` (full `${{ }}` template) or `message` + `include` (message text plus resolved data paths).
+</completion_messages>
+
+<artifacts>
+Workflows can write post-completion files via the `artifacts` field. Paths may contain `${{ }}` expressions. Artifacts targeting `.project/*.json` are routed through `writeBlock()` for schema validation.
+
+Block artifact write failures are fatal — if the data doesn't conform to the block's schema, the workflow fails. Non-block artifact failures remain non-fatal (warning). On resume, all steps are preserved; only artifact processing re-runs, so fixing the schema issue or agent output and resuming avoids re-running expensive LLM steps.
+</artifacts>
+
+<validation>
+`validateWorkflow(spec, cwd)` runs authoring-time checks without executing the workflow:
+
+1. **Agent resolution** — all referenced agents exist in the three-tier search
+2. **Monitor resolution** — all referenced monitors exist in .pi/monitors/ or built-in examples
+3. **Schema resolution** — all output schema file paths resolve to existing files
+4. **Step reference validity** — `${{ steps.X }}` expressions reference declared steps
+5. **Step ordering** — referenced steps are declared before the referencing step
+6. **Filter name validity** — `${{ value | filter }}` uses known filter names
+
+Returns `{ valid: boolean, issues: ValidationIssue[] }` where each issue has severity, message, and field path. Use `/workflow validate` or `/workflow validate <name>` to run from the command line.
+</validation>
+
+<success_criteria>
+- Workflow completes all steps without unhandled failures
+- Step outputs match declared output schemas
+- State is persisted atomically after each step
+- Completion message is delivered to main conversation
+- `/workflow validate` returns no errors for authored specs
+- Checkpoint/resume recovers from the last completed step
+</success_criteria>
+
+*Generated from source by `scripts/generate-skills.js` — do not edit by hand.*

package/skills/pi-workflows/references/bundled-resources.md

@@ -0,0 +1,87 @@
+# Bundled Resources
+
+## agents/ (21 files)
+
+- `agents/architecture-designer.agent.yaml`
+- `agents/architecture-inferrer.agent.yaml`
+- `agents/audit-fixer.agent.yaml`
+- `agents/code-explorer.agent.yaml`
+- `agents/decomposer.agent.yaml`
+- `agents/gap-identifier.agent.yaml`
+- `agents/handoff-writer.agent.yaml`
+- `agents/investigator.agent.yaml`
+- `agents/pattern-analyzer.agent.yaml`
+- `agents/phase-author.agent.yaml`
+- `agents/plan-creator.agent.yaml`
+- `agents/plan-decomposer.agent.yaml`
+- `agents/project-definer.agent.yaml`
+- `agents/project-inferrer.agent.yaml`
+- `agents/quality-analyzer.agent.yaml`
+- `agents/requirements-gatherer.agent.yaml`
+- `agents/researcher.agent.yaml`
+- `agents/spec-implementer.agent.yaml`
+- `agents/structure-analyzer.agent.yaml`
+- `agents/synthesizer.agent.yaml`
+- `agents/verifier.agent.yaml`
+
+## schemas/ (11 files)
+
+- `schemas/decomposition-specs.schema.json`
+- `schemas/execution-results.schema.json`
+- `schemas/investigation-findings.schema.json`
+- `schemas/pattern-analysis.schema.json`
+- `schemas/phase.schema.json`
+- `schemas/plan-breakdown.schema.json`
+- `schemas/quality-analysis.schema.json`
+- `schemas/research-findings.schema.json`
+- `schemas/structure-analysis.schema.json`
+- `schemas/synthesis.schema.json`
+- `schemas/verifier-output.schema.json`
+
+## workflows/ (14 files)
+
+- `workflows/analyze-existing-project.workflow.yaml`
+- `workflows/create-handoff.workflow.yaml`
+- `workflows/create-phase.workflow.yaml`
+- `workflows/do-gap.workflow.yaml`
+- `workflows/fix-audit.workflow.yaml`
+- `workflows/gap-to-phase.workflow.yaml`
+- `workflows/init-new-project.workflow.yaml`
+- `workflows/parallel-analysis.workflow.yaml`
+- `workflows/parallel-explicit.workflow.yaml`
+- `workflows/pausable-analysis.workflow.yaml`
+- `workflows/plan-from-requirements.workflow.yaml`
+- `workflows/resumable-analysis.workflow.yaml`
+- `workflows/self-implement.workflow.yaml`
+- `workflows/typed-analysis.workflow.yaml`
+
+## templates/ (28 files)
+
+- `templates/analyzers/base-analyzer.md`
+- `templates/analyzers/macros.md`
+- `templates/analyzers/patterns-task.md`
+- `templates/analyzers/patterns.md`
+- `templates/analyzers/quality-task.md`
+- `templates/analyzers/quality.md`
+- `templates/analyzers/structure-task.md`
+- `templates/analyzers/structure.md`
+- `templates/architecture-designer/task.md`
+- `templates/architecture-inferrer/task.md`
+- `templates/audit-fixer/task.md`
+- `templates/decomposer/task.md`
+- `templates/explorer/system.md`
+- `templates/explorer/task.md`
+- `templates/gap-identifier/task.md`
+- `templates/handoff-writer/task.md`
+- `templates/investigator/task.md`
+- `templates/phase-author/task.md`
+- `templates/plan-creator/task.md`
+- `templates/plan-decomposer/task.md`
+- `templates/project-definer/task.md`
+- `templates/project-inferrer/task.md`
+- `templates/requirements-gatherer/task.md`
+- `templates/researcher/task.md`
+- `templates/spec-implementer/task.md`
+- `templates/synthesizer/system.md`
+- `templates/synthesizer/task.md`
+- `templates/verifier/task.md`

package/workflows-extension.ts

@@ -1 +1 @@
-export { default } from "@davidorex/pi-workflows/src/index.ts";
+export { default } from "@davidorex/pi-workflows";