@wefter/opencode 0.2.0 → 0.2.1

package/src/workflows/product-shaping/templates/prompts/intake-prompt.md

@@ -1,30 +1,30 @@
-# Product Shaping Intake
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-- {{CONFIG_PATH}}
-- {{SPEC_ROOT}}/README.md when present
-
-Write or repair only intake artifacts under {{SPEC_ROOT}}.
-
-Required files:
-
-{{REQUIRED_FILES}}
-
-Responsibilities:
-
-- Create or update `README.md`, `discovery/SOURCE_MATERIALS.md`, `discovery/IDEA_BRIEF.md` and `discovery/OPEN_QUESTIONS.md`.
-- Do not edit artifacts outside those intake files.
-- Preserve raw source material as source material; do not turn it into scope, roadmap, domain rules or deliverables.
-- Record unresolved questions in {{OPEN_QUESTIONS_PATH}}.
-
-Stop conditions:
-
-- Problem, user or expected value is unclear.
-- A decision-relevant idea lacks source material, market reference or recorded product decision.
-- The work requires roadmap, release scope, deliverables or technical decisions.
+# Product Shaping Intake
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+- {{CONFIG_PATH}}
+- {{SPEC_ROOT}}/README.md when present
+
+Write or repair only intake artifacts under {{SPEC_ROOT}}.
+
+Required files:
+
+{{REQUIRED_FILES}}
+
+Responsibilities:
+
+- Create or update `README.md`, `discovery/SOURCE_MATERIALS.md`, `discovery/IDEA_BRIEF.md` and `discovery/OPEN_QUESTIONS.md`.
+- Do not edit artifacts outside those intake files.
+- Preserve raw source material as source material; do not turn it into scope, roadmap, domain rules or deliverables.
+- Record unresolved questions in {{OPEN_QUESTIONS_PATH}}.
+
+Stop conditions:
+
+- Problem, user or expected value is unclear.
+- A decision-relevant idea lacks source material, market reference or recorded product decision.
+- The work requires roadmap, release scope, deliverables or technical decisions.

package/src/workflows/product-shaping/templates/prompts/product-auditor-prompt.md

@@ -1,53 +1,53 @@
-# Product Shaping Auditor
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read operating instructions first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-
-Read product specs in hard utilization order:
-
-- {{SPEC_ROOT}}/README.md
-- {{SPEC_ROOT}}/releases/{{RELEASE_ID}}/README.md
-- {{SPEC_ROOT}}/PRODUCT_VISION.md
-- {{PRODUCT_DECISIONS_PATH}}
-- {{SCOPE_PATH}}
-- {{DOMAIN_SPEC_PATH}}
-- {{ACCEPTANCE_CRITERIA_PATH}}
-- {{DELIVERABLES_PATH}}
-- {{SPEC_ROOT}}/product/DOMAIN_MODEL.md
-- {{SPEC_ROOT}}/product/OPERATIONAL_FLOW.md
-- {{SPEC_ROOT}}/product/FEATURE_CATALOG.md
-- {{SPEC_ROOT}}/product/MODULE_ROADMAP.md
-- {{OPEN_QUESTIONS_PATH}}
-- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
-- {{SPEC_ROOT}}/references/README.md
-- {{SPEC_ROOT}}/references/<reference>.md files when present
-
-Then inspect supporting source material:
-
-- {{SPEC_ROOT}}/discovery/SOURCE_MATERIALS.md
-- {{SPEC_ROOT}}/releases/README.md
-
-Responsibilities:
-
-- Find contradiction, omission, overreach, ambiguity and drift.
-- Validate every required file against its responsibility, limits and traceability obligations.
-- Apply precedence rules only to classify conflicts, not to silently repair them.
-- Write adversarial review evidence to {{ADVERSARIAL_REVIEW_PATH}}.
-
-Do not edit source specs while auditing.
-
-Blocking findings include:
-
-- Release scope contradicted by domain spec, acceptance criteria or deliverables.
-- Blocking open questions hidden outside {{OPEN_QUESTIONS_PATH}}.
-- Deliverables that contain task specs or implementation steps.
-
-Passing evidence format:
-
-- Include `Status: pass` only if there are no blocking findings.
-- Include `Blocking findings: none` only when the review found no blockers.
+# Product Shaping Auditor
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read operating instructions first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+
+Read product specs in hard utilization order:
+
+- {{SPEC_ROOT}}/README.md
+- {{SPEC_ROOT}}/releases/{{RELEASE_ID}}/README.md
+- {{SPEC_ROOT}}/PRODUCT_VISION.md
+- {{PRODUCT_DECISIONS_PATH}}
+- {{SCOPE_PATH}}
+- {{DOMAIN_SPEC_PATH}}
+- {{ACCEPTANCE_CRITERIA_PATH}}
+- {{DELIVERABLES_PATH}}
+- {{SPEC_ROOT}}/product/DOMAIN_MODEL.md
+- {{SPEC_ROOT}}/product/OPERATIONAL_FLOW.md
+- {{SPEC_ROOT}}/product/FEATURE_CATALOG.md
+- {{SPEC_ROOT}}/product/MODULE_ROADMAP.md
+- {{OPEN_QUESTIONS_PATH}}
+- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
+- {{SPEC_ROOT}}/references/README.md
+- {{SPEC_ROOT}}/references/<reference>.md files when present
+
+Then inspect supporting source material:
+
+- {{SPEC_ROOT}}/discovery/SOURCE_MATERIALS.md
+- {{SPEC_ROOT}}/releases/README.md
+
+Responsibilities:
+
+- Find contradiction, omission, overreach, ambiguity and drift.
+- Validate every required file against its responsibility, limits and traceability obligations.
+- Apply precedence rules only to classify conflicts, not to silently repair them.
+- Write adversarial review evidence to {{ADVERSARIAL_REVIEW_PATH}}.
+
+Do not edit source specs while auditing.
+
+Blocking findings include:
+
+- Release scope contradicted by domain spec, acceptance criteria or deliverables.
+- Blocking open questions hidden outside {{OPEN_QUESTIONS_PATH}}.
+- Deliverables that contain task specs or implementation steps.
+
+Passing evidence format:
+
+- Include `Status: pass` only if there are no blocking findings.
+- Include `Blocking findings: none` only when the review found no blockers.

package/src/workflows/product-shaping/templates/prompts/product-repairer-prompt.md

@@ -1,25 +1,25 @@
-# Product Shaping Repairer
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-- {{SPEC_ROOT}}/README.md
-- Latest audit or validation finding under {{RUN_ROOT}}
-- Affected source specs under {{SPEC_ROOT}}
-
-Responsibilities:
-
-- Repair candidate or approved product artifacts that violate doctrine.
-- Preserve conflict evidence and cite the finding being repaired.
-- Stop when repair would require a new product decision.
-
-Do not:
-
-- Change raw source materials.
-- Erase evidence of conflict.
-- Invent scope, domain behavior, acceptance criteria or deliverables.
-- Create task specs.
+# Product Shaping Repairer
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+- {{SPEC_ROOT}}/README.md
+- Latest audit or validation finding under {{RUN_ROOT}}
+- Affected source specs under {{SPEC_ROOT}}
+
+Responsibilities:
+
+- Repair candidate or approved product artifacts that violate doctrine.
+- Preserve conflict evidence and cite the finding being repaired.
+- Stop when repair would require a new product decision.
+
+Do not:
+
+- Change raw source materials.
+- Erase evidence of conflict.
+- Invent scope, domain behavior, acceptance criteria or deliverables.
+- Create task specs.

package/src/workflows/product-shaping/templates/prompts/product-shaper-prompt.md

@@ -1,26 +1,26 @@
-# Product Shaper
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-- {{SPEC_ROOT}}/README.md
-- {{SPEC_ROOT}}/PRODUCT_VISION.md when present
-- {{SPEC_ROOT}}/references/README.md when present
-- {{OPEN_QUESTIONS_PATH}}
-- {{PRODUCT_DECISIONS_PATH}}
-
-Responsibilities:
-
-- Create or update `PRODUCT_VISION.md`, `product/FEATURE_CATALOG.md` and `product/MODULE_ROADMAP.md`.
-- Record accepted, superseded or rejected product direction decisions in {{PRODUCT_DECISIONS_PATH}}.
-- Keep the feature catalog out of backlog, roadmap and release-scope responsibilities.
-- Use only valid feature statuses: `candidate`, `core`, `future`, `rejected`, `needs-decision`.
-
-Stop conditions:
-
-- A future, rejected or needs-decision feature is about to enter release scope without explicit product decision.
-- A product decision is needed to choose direction, priority or tradeoff.
+# Product Shaper
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+- {{SPEC_ROOT}}/README.md
+- {{SPEC_ROOT}}/PRODUCT_VISION.md when present
+- {{SPEC_ROOT}}/references/README.md when present
+- {{OPEN_QUESTIONS_PATH}}
+- {{PRODUCT_DECISIONS_PATH}}
+
+Responsibilities:
+
+- Create or update `PRODUCT_VISION.md`, `product/FEATURE_CATALOG.md` and `product/MODULE_ROADMAP.md`.
+- Record accepted, superseded or rejected product direction decisions in {{PRODUCT_DECISIONS_PATH}}.
+- Keep the feature catalog out of backlog, roadmap and release-scope responsibilities.
+- Use only valid feature statuses: `candidate`, `core`, `future`, `rejected`, `needs-decision`.
+
+Stop conditions:
+
+- A future, rejected or needs-decision feature is about to enter release scope without explicit product decision.
+- A product decision is needed to choose direction, priority or tradeoff.

package/src/workflows/product-shaping/templates/prompts/product-validator-prompt.md

@@ -1,55 +1,55 @@
-# Product Shaping Validator
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read operating instructions first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-
-Read product specs in hard utilization order:
-
-- {{SPEC_ROOT}}/README.md
-- {{SPEC_ROOT}}/releases/{{RELEASE_ID}}/README.md
-- {{SPEC_ROOT}}/PRODUCT_VISION.md
-- {{PRODUCT_DECISIONS_PATH}}
-- {{SCOPE_PATH}}
-- {{DOMAIN_SPEC_PATH}}
-- {{ACCEPTANCE_CRITERIA_PATH}}
-- {{DELIVERABLES_PATH}}
-- {{SPEC_ROOT}}/product/DOMAIN_MODEL.md
-- {{SPEC_ROOT}}/product/OPERATIONAL_FLOW.md
-- {{SPEC_ROOT}}/product/FEATURE_CATALOG.md
-- {{SPEC_ROOT}}/product/MODULE_ROADMAP.md
-- {{OPEN_QUESTIONS_PATH}}
-- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
-- {{SPEC_ROOT}}/references/README.md
-- {{SPEC_ROOT}}/references/<reference>.md files when present
-
-Then inspect supporting source material:
-
-- {{SPEC_ROOT}}/discovery/SOURCE_MATERIALS.md
-- {{SPEC_ROOT}}/releases/README.md
-
-Validate:
-
-- Every required file exists or is explicitly blocked.
-- Every required file respects its responsibility and limits.
-- {{OPEN_QUESTIONS_PATH}} has no unresolved blocker for {{RELEASE_ID}}.
-- {{SCOPE_PATH}}, {{DOMAIN_SPEC_PATH}}, {{ACCEPTANCE_CRITERIA_PATH}} and {{DELIVERABLES_PATH}} are consistent.
-- Every implementation-intended deliverable is `ready`.
-- {{DELIVERABLES_PATH}} is the only handoff to delivery implementation.
-- Applicable documentation-audit drift findings have been reviewed and resolved, marked not applicable, or recorded as blockers/human decisions.
-- Adversarial review evidence exists at {{ADVERSARIAL_REVIEW_PATH}}.
-- Final validation evidence is written at {{FINAL_VALIDATION_PATH}}.
-
-Write final validation under {{RUN_ROOT}}/final, specifically {{FINAL_VALIDATION_PATH}}.
-
-Passing evidence format:
-
-- Include `Status: pass` only if all completion gate checks pass.
-- Include `Ready for delivery implementation: yes` only when {{DELIVERABLES_PATH}} is valid as the delivery handoff.
-- Include `Documentation drift findings reviewed: yes` only after applicable documentation-audit drift findings were checked.
-
-Do not pass validation with unresolved conflicts, missing required files or blocking questions.
+# Product Shaping Validator
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read operating instructions first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+
+Read product specs in hard utilization order:
+
+- {{SPEC_ROOT}}/README.md
+- {{SPEC_ROOT}}/releases/{{RELEASE_ID}}/README.md
+- {{SPEC_ROOT}}/PRODUCT_VISION.md
+- {{PRODUCT_DECISIONS_PATH}}
+- {{SCOPE_PATH}}
+- {{DOMAIN_SPEC_PATH}}
+- {{ACCEPTANCE_CRITERIA_PATH}}
+- {{DELIVERABLES_PATH}}
+- {{SPEC_ROOT}}/product/DOMAIN_MODEL.md
+- {{SPEC_ROOT}}/product/OPERATIONAL_FLOW.md
+- {{SPEC_ROOT}}/product/FEATURE_CATALOG.md
+- {{SPEC_ROOT}}/product/MODULE_ROADMAP.md
+- {{OPEN_QUESTIONS_PATH}}
+- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
+- {{SPEC_ROOT}}/references/README.md
+- {{SPEC_ROOT}}/references/<reference>.md files when present
+
+Then inspect supporting source material:
+
+- {{SPEC_ROOT}}/discovery/SOURCE_MATERIALS.md
+- {{SPEC_ROOT}}/releases/README.md
+
+Validate:
+
+- Every required file exists or is explicitly blocked.
+- Every required file respects its responsibility and limits.
+- {{OPEN_QUESTIONS_PATH}} has no unresolved blocker for {{RELEASE_ID}}.
+- {{SCOPE_PATH}}, {{DOMAIN_SPEC_PATH}}, {{ACCEPTANCE_CRITERIA_PATH}} and {{DELIVERABLES_PATH}} are consistent.
+- Every implementation-intended deliverable is `ready`.
+- {{DELIVERABLES_PATH}} is the only handoff to delivery implementation.
+- Applicable documentation-audit drift findings have been reviewed and resolved, marked not applicable, or recorded as blockers/human decisions.
+- Adversarial review evidence exists at {{ADVERSARIAL_REVIEW_PATH}}.
+- Final validation evidence is written at {{FINAL_VALIDATION_PATH}}.
+
+Write final validation under {{RUN_ROOT}}/final, specifically {{FINAL_VALIDATION_PATH}}.
+
+Passing evidence format:
+
+- Include `Status: pass` only if all completion gate checks pass.
+- Include `Ready for delivery implementation: yes` only when {{DELIVERABLES_PATH}} is valid as the delivery handoff.
+- Include `Documentation drift findings reviewed: yes` only after applicable documentation-audit drift findings were checked.
+
+Do not pass validation with unresolved conflicts, missing required files or blocking questions.

package/src/workflows/product-shaping/templates/prompts/reference-research-prompt.md

@@ -1,25 +1,25 @@
-# Product Shaping Reference Research
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-- {{SPEC_ROOT}}/README.md
-- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
-- {{OPEN_QUESTIONS_PATH}}
-
-Responsibilities:
-
-- Create or update `references/<reference>.md` and `references/README.md`.
-- Mark external observations as inspiration, not commitments.
-- Record research date, confidence and freshness notes.
-
-Do not:
-
-- Convert competitor behavior into product requirements.
-- Create release scope, acceptance criteria, deliverables or task specs.
-
-Output must remain under {{SPEC_ROOT}} and runtime notes must remain under {{RUN_ROOT}}.
+# Product Shaping Reference Research
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+- {{SPEC_ROOT}}/README.md
+- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
+- {{OPEN_QUESTIONS_PATH}}
+
+Responsibilities:
+
+- Create or update `references/<reference>.md` and `references/README.md`.
+- Mark external observations as inspiration, not commitments.
+- Record research date, confidence and freshness notes.
+
+Do not:
+
+- Convert competitor behavior into product requirements.
+- Create release scope, acceptance criteria, deliverables or task specs.
+
+Output must remain under {{SPEC_ROOT}} and runtime notes must remain under {{RUN_ROOT}}.

package/src/workflows/product-shaping/templates/prompts/release-planner-prompt.md

@@ -1,34 +1,34 @@
-# Product Release Planner
-
-Run: {{RUN_ID}}
-Release: {{RELEASE_ID}}
-
-Read first:
-
-- {{PROCESS_DOC_PATH}}
-- {{CONTRACT_PATH}}
-- {{SPEC_ROOT}}/README.md
-- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
-- {{SPEC_ROOT}}/product/FEATURE_CATALOG.md
-- {{SPEC_ROOT}}/product/MODULE_ROADMAP.md
-- {{SPEC_ROOT}}/releases/README.md when present
-- {{SPEC_ROOT}}/releases/{{RELEASE_ID}}/README.md when present
-- {{SPEC_ROOT}}/PRODUCT_VISION.md
-- {{PRODUCT_DECISIONS_PATH}}
-- {{SCOPE_PATH}} when present
-- {{DOMAIN_SPEC_PATH}} when present
-- {{ACCEPTANCE_CRITERIA_PATH}} when present
-- {{OPEN_QUESTIONS_PATH}}
-
-Responsibilities:
-
-- Create or update `releases/README.md`, release `README.md`, {{SCOPE_PATH}}, {{ACCEPTANCE_CRITERIA_PATH}} and {{DELIVERABLES_PATH}}.
-- Record accepted, superseded or rejected scope, acceptance or deliverable decisions in {{PRODUCT_DECISIONS_PATH}}.
-- Keep {{SCOPE_PATH}} as source of truth for included and excluded release scope.
-- Keep {{DELIVERABLES_PATH}} at deliverable granularity.
-- Edit only release planning artifacts and report required upstream product/domain repairs instead of making them directly.
-
-Do not:
-
-- Create task specs, delivery plans, code instructions or TDD task sequences.
-- Add deliverables outside scope without recording a pending scope change.
+# Product Release Planner
+
+Run: {{RUN_ID}}
+Release: {{RELEASE_ID}}
+
+Read first:
+
+- {{PROCESS_DOC_PATH}}
+- {{CONTRACT_PATH}}
+- {{SPEC_ROOT}}/README.md
+- {{SPEC_ROOT}}/discovery/IDEA_BRIEF.md
+- {{SPEC_ROOT}}/product/FEATURE_CATALOG.md
+- {{SPEC_ROOT}}/product/MODULE_ROADMAP.md
+- {{SPEC_ROOT}}/releases/README.md when present
+- {{SPEC_ROOT}}/releases/{{RELEASE_ID}}/README.md when present
+- {{SPEC_ROOT}}/PRODUCT_VISION.md
+- {{PRODUCT_DECISIONS_PATH}}
+- {{SCOPE_PATH}} when present
+- {{DOMAIN_SPEC_PATH}} when present
+- {{ACCEPTANCE_CRITERIA_PATH}} when present
+- {{OPEN_QUESTIONS_PATH}}
+
+Responsibilities:
+
+- Create or update `releases/README.md`, release `README.md`, {{SCOPE_PATH}}, {{ACCEPTANCE_CRITERIA_PATH}} and {{DELIVERABLES_PATH}}.
+- Record accepted, superseded or rejected scope, acceptance or deliverable decisions in {{PRODUCT_DECISIONS_PATH}}.
+- Keep {{SCOPE_PATH}} as source of truth for included and excluded release scope.
+- Keep {{DELIVERABLES_PATH}} at deliverable granularity.
+- Edit only release planning artifacts and report required upstream product/domain repairs instead of making them directly.
+
+Do not:
+
+- Create task specs, delivery plans, code instructions or TDD task sequences.
+- Add deliverables outside scope without recording a pending scope change.

package/src/workflows/product-shaping/workflow.json

@@ -1,33 +1,33 @@
-{
-  "id": "product-shaping",
-  "status": "available",
-  "title": "Product Shaping",
-  "summary": "Shapes an initial product idea into explicit product vision, scope, feature catalog, decisions and acceptance criteria before technical design.",
-  "commands": {
-    "cli": ["wefter product shape", "wefter product validate"],
-    "opencode": ["/wefter-shape-product"]
-  },
-  "commandAvailability": "Commands are installed by default. Set workflows.product-shaping.enabled to false to disable local execution.",
-  "defaultRoots": {
-    "specRoot": ".wefter/specs",
-    "workflowRoot": ".wefter/workflows",
-    "runRoot": ".wefter/runs/product-shaping"
-  },
-  "contracts": [
-    "contracts/product-spec-contract.json"
-  ],
-  "compatibility": [
-    "compatibility.md"
-  ],
-  "auditProfiles": [
-    "templates/documentation-audit-profile.json"
-  ],
-  "artifactLayout": [
-    "prompts/",
-    "draft/",
-    "review/",
-    "validation/",
-    "final/"
-  ],
-  "writesSourceFiles": true
-}
+{
+  "id": "product-shaping",
+  "status": "available",
+  "title": "Product Shaping",
+  "summary": "Shapes an initial product idea into explicit product vision, scope, feature catalog, decisions and acceptance criteria before technical design.",
+  "commands": {
+    "cli": ["wefter product shape", "wefter product validate"],
+    "opencode": ["/wefter-shape-product"]
+  },
+  "commandAvailability": "Commands are installed by default. Set workflows.product-shaping.enabled to false to disable local execution.",
+  "defaultRoots": {
+    "specRoot": ".wefter/specs",
+    "workflowRoot": ".wefter/workflows",
+    "runRoot": ".wefter/runs/product-shaping"
+  },
+  "contracts": [
+    "contracts/product-spec-contract.json"
+  ],
+  "compatibility": [
+    "compatibility.md"
+  ],
+  "auditProfiles": [
+    "templates/documentation-audit-profile.json"
+  ],
+  "artifactLayout": [
+    "prompts/",
+    "draft/",
+    "review/",
+    "validation/",
+    "final/"
+  ],
+  "writesSourceFiles": true
+}

package/src/workflows/technical-shaping/README.md

@@ -1,5 +1,7 @@
-# Technical Shaping
-
-Planned workflow for converting shaped product documentation into technical decisions and implementation constraints.
-
-It is registered from the start, but implementation comes after `documentation-audit` and `work-unit-implementation` are stable.
+# Technical Shaping
+
+Planned workflow for converting shaped product documentation into technical decisions and implementation constraints.
+
+It is registered from the start, but implementation comes after `documentation-audit` and `work-unit-implementation` are stable.
+
+No CLI or OpenCode command is installed while this workflow is planned. Future command names may appear only as planning metadata, not executable workflow contract.

package/src/workflows/technical-shaping/workflow.json

@@ -1,10 +1,14 @@
-{
-  "id": "technical-shaping",
-  "status": "planned",
-  "title": "Technical Shaping",
-  "summary": "Shapes product documentation into explicit technical decisions, implementation constraints, data contracts and verification expectations.",
-  "commands": {
-    "cli": ["wefter technical shape"],
-    "opencode": ["/wefter-shape-technical"]
-  }
-}
+{
+  "id": "technical-shaping",
+  "status": "planned",
+  "title": "Technical Shaping",
+  "summary": "Shapes product documentation into explicit technical decisions, implementation constraints, data contracts and verification expectations.",
+  "commands": {
+    "cli": [],
+    "opencode": []
+  },
+  "plannedCommands": {
+    "cli": ["wefter technical shape"],
+    "opencode": ["/wefter-shape-technical"]
+  }
+}