@manhd_d/ai-harness 0.12.0 → 0.13.0

package/capabilities/analysis/capability.json

@@ -0,0 +1,48 @@
+{
+  "schema_version": 1,
+  "id": "analysis",
+  "description": "Requirements, domain rules, AC, traceability and living technical docs. Canonical Product assets; selective context.",
+  "skills": [
+    "harness-product-knowledge-analysis",
+    "harness-product-business-analysis",
+    "harness-product-brd-generation",
+    "harness-product-user-stories",
+    "harness-product-acceptance-criteria",
+    "harness-product-backlog-prioritization",
+    "harness-product-traceability",
+    "harness-product-document-review",
+    "harness-product-srs-generation",
+    "harness-product-use-case-generation",
+    "harness-product-techspec"
+  ],
+  "workflows": [
+    "workflows/document-driven.md",
+    "workflows/confluence-to-spec.md",
+    "workflows/change-impact-analysis.md",
+    "workflows/techspec-maintenance.md",
+    "workflows/product-to-solution.md"
+  ],
+  "agents": [
+    "agents/business-analyst.md",
+    "agents/requirements-reviewer.md"
+  ],
+  "templates": [
+    "templates/source-register.md",
+    "templates/brd.md",
+    "templates/business-rules.md",
+    "templates/backlog.md",
+    "templates/acceptance-criteria.md",
+    "templates/traceability.md",
+    "templates/review-report.md",
+    "templates/decision-log.md",
+    "templates/srs.md",
+    "templates/use-cases.md",
+    "templates/techspec.md"
+  ],
+  "module_version": "1.0.0",
+  "verification": "checks/verification.json",
+  "evaluation": "evals/cases.json",
+  "template_aliases": {},
+  "agent_aliases": {},
+  "asset_owner": "product"
+}

package/capabilities/analysis/checks/verification.json

@@ -0,0 +1,16 @@
+{
+  "schema_version": 1,
+  "checks": [
+    {
+      "id": "profile-handoff",
+      "title": "Review analysis agent inputs/output and decisions",
+      "command": [],
+      "when_file": null,
+      "evidence": [
+        "Canonical sources and proportional scope",
+        "Actual owner decisions, evidence and next role"
+      ],
+      "execution": "manual"
+    }
+  ]
+}

package/capabilities/analysis/evals/cases.json

@@ -0,0 +1,15 @@
+{
+  "schema_version": 1,
+  "cases": [
+    {
+      "id": "profile-scope",
+      "prompt": "Use only selected analysis skills for a project with approved sources.",
+      "criteria": [
+        "Load selected canonical skills only",
+        "Preserve source policy and decisions",
+        "Handoff missing optional perspectives without claiming another agent ran"
+      ],
+      "critical": true
+    }
+  ]
+}

package/capabilities/architecture/agents/architecture-reviewer.md

@@ -14,3 +14,8 @@ Review-only unless asked to fix; author self-review is not independent review. A
 ## Handoff
 Return requirements gaps to BA/PO, design gaps to SA, sequencing risks to PM and defects to Dev/QA; include actual source and uncertainty.
 Load relevant skills by description; do not assume another agent is running.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-architecture-review`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/architecture/agents/solution-architect.md

@@ -14,3 +14,8 @@ May inspect and propose within authorized scope. Cannot self-approve stakeholder
 ## Handoff
 Pass requirement/NFR/ADR IDs, public boundaries, source revisions, acceptance/verification and risks to Delivery/Core/adapters. Return scope questions to BA/PO and operational gaps to DevOps.
 Load relevant skills by description; do not assume another agent is running.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-architecture-project-context`, `harness-architecture-quality-attributes`, `harness-architecture-solution-design`, `harness-architecture-decision-records`, `harness-architecture-change-impact`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/architecture/capability.json

@@ -26,7 +26,7 @@
     "workflows/discovery-to-design.md",
     "workflows/change-review.md"
   ],
-  "module_version": "1.1.0",
+  "module_version": "1.2.0",
   "recommends": [
     "capability:product"
   ],

package/capabilities/delivery/agents/project-manager.md

@@ -1,16 +1,15 @@
-# Project Manager
-
-Tool-neutral role contract; one host can perform roles sequentially.
+# Project Manager — compatibility alias
 
 ## Inputs
-Reviewed MVP/backlog, SA decisions, dependency graph, team estimates/capacity and actual progress.
-
+Read the canonical project contract .harness/core/agents/project-manager.md with accepted scope, design, estimates and actual progress.
 ## Outputs
-Delivery plan, risk register, change assessment and evidence-based status drafts.
-
+The canonical PM delivery plan, risk/status and checkpoint handoff. This alias does not create another worker.
 ## Permissions and limits
-Dates, budgets and assignments remain proposals until confirmed. No invented velocity/progress; no messaging/calendar updates, merge or deploy without authorization.
-
+Apply the canonical contract and actual host permissions. Existing configured role IDs/model overrides remain valid.
 ## Handoff
-Return value/scope decisions to PO, design dependencies to SA, release gates to DevOps and approved slices to Core implementation; record actual evidence and blockers.
-Load relevant skills by description; do not assume another agent is running.
+Use the canonical PM contract; preserve existing documents and IDs.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-delivery-planning`, `harness-delivery-risk-management`, `harness-delivery-scope-change`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/delivery/capability.json

@@ -19,11 +19,17 @@
     "workflows/planning.md",
     "workflows/execution-change.md"
   ],
-  "module_version": "1.1.0",
+  "module_version": "1.2.0",
   "recommends": [
     "capability:product",
     "capability:architecture"
   ],
   "verification": "checks/verification.json",
-  "evaluation": "evals/cases.json"
+  "evaluation": "evals/cases.json",
+  "template_aliases": {
+    "templates/delivery-plan.md": "templates/delivery-plan.md"
+  },
+  "agent_aliases": {
+    "agents/project-manager.md": "core/agents/project-manager.md"
+  }
 }

package/capabilities/delivery/templates/delivery-plan.md

@@ -1,25 +1,4 @@
-# Delivery plan
+# Delivery plan — compatibility template
 
 Status: draft / pending review
-Owner: TODO
-Sources and revisions: TODO
-Scope / related requirement and decision IDs: TODO
-Last verified against code: TODO (or not applicable with reason)
-
-## Baseline and authority
-Reviewed MVP/AC, architecture/source revisions, confirmed estimates/capacity or explicitly unknown.
-## Value slices and dependencies
-| Slice / user outcome | AC / OpenSpec tasks | Prerequisites / owner | Estimate source / range | Completion evidence |
-| --- | --- | --- | --- | --- |
-| TODO | TODO | TODO | unknown | pending |
-## Milestones
-Order and integration/repository merge sequence; dates are proposals with sources, not invented commitments.
-## Verification and release
-Quality gates, migration, deployment/rollback owners and feedback checkpoints; link DevOps plan.
-## Status and risks
-Actual completed evidence, blocked/pending work, risk-register links and next owner.
-
-
-## Review and handoff
-Record actual owner decisions, unresolved consequential questions, verification performed/skipped,
-next role, source/output paths and affected OpenSpec change. Draft text is not an accepted decision.
+Canonical template: .harness/templates/delivery-plan.md. Existing document paths remain project-owned; new-doc resolves this alias without migrating old documents.

package/capabilities/discovery/capability.json

@@ -0,0 +1,37 @@
+{
+  "schema_version": 1,
+  "id": "discovery",
+  "description": "Idea/research, product direction, MVP and outcomes. Canonical Product assets; selective context.",
+  "skills": [
+    "harness-product-idea-discovery",
+    "harness-product-product-research",
+    "harness-product-mvp-definition",
+    "harness-product-prd-generation",
+    "harness-product-product-outcomes"
+  ],
+  "workflows": [
+    "workflows/idea-driven.md",
+    "workflows/idea-to-prd.md",
+    "workflows/product-to-solution.md"
+  ],
+  "agents": [
+    "agents/product-manager.md",
+    "agents/product-owner.md"
+  ],
+  "templates": [
+    "templates/idea.md",
+    "templates/research.md",
+    "templates/product-brief.md",
+    "templates/prd.md",
+    "templates/prd-lite.md",
+    "templates/mvp.md",
+    "templates/outcomes.md",
+    "templates/decision-log.md"
+  ],
+  "module_version": "1.0.0",
+  "verification": "checks/verification.json",
+  "evaluation": "evals/cases.json",
+  "template_aliases": {},
+  "agent_aliases": {},
+  "asset_owner": "product"
+}

package/capabilities/discovery/checks/verification.json

@@ -0,0 +1,16 @@
+{
+  "schema_version": 1,
+  "checks": [
+    {
+      "id": "profile-handoff",
+      "title": "Review discovery agent inputs/output and decisions",
+      "command": [],
+      "when_file": null,
+      "evidence": [
+        "Canonical sources and proportional scope",
+        "Actual owner decisions, evidence and next role"
+      ],
+      "execution": "manual"
+    }
+  ]
+}

package/capabilities/discovery/evals/cases.json

@@ -0,0 +1,15 @@
+{
+  "schema_version": 1,
+  "cases": [
+    {
+      "id": "profile-scope",
+      "prompt": "Use only selected discovery skills for a project with approved sources.",
+      "criteria": [
+        "Load selected canonical skills only",
+        "Preserve source policy and decisions",
+        "Handoff missing optional perspectives without claiming another agent ran"
+      ],
+      "critical": true
+    }
+  ]
+}

package/capabilities/product/agents/business-analyst.md

@@ -16,3 +16,8 @@ Hand reviewed requirements and source references to Product Manager and Product
 
 Pass source revisions, business rules, FR/US/AC/NFR IDs, contradictions and approval status to PO;
 use product-to-solution for accepted scope and return technical assumptions to Architecture.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-product-knowledge-analysis`, `harness-product-business-analysis`, `harness-product-srs-generation`, `harness-product-use-case-generation`, `harness-product-acceptance-criteria`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/product/agents/product-manager.md

@@ -13,3 +13,8 @@ Do not fabricate user research, revenue metrics or release commitments. All prio
 
 ## Handoff
 Hand PRD, measurable outcomes and tradeoffs to Product Owner; request named product sign-off.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-product-idea-discovery`, `harness-product-product-research`, `harness-product-prd-generation`, `harness-product-product-outcomes`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/product/agents/product-owner.md

@@ -17,3 +17,8 @@ Hand approved stories and traceable AC to UI/UX and OpenSpec; return gaps to BA/
 
 Use product-to-solution workflow and MVP/outcomes skills; actual stakeholder decisions remain required
 for consequential scope choices. Send requirement/AC/NFR IDs and decision evidence to Architecture/Delivery.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-product-mvp-definition`, `harness-product-backlog-prioritization`, `harness-product-user-stories`, `harness-product-acceptance-criteria`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/product/agents/project-manager.md

@@ -1,20 +1,15 @@
-# Project Manager
-
-Coordinates delivery planning, sequencing, stakeholder communications, dependencies and risks.
+# Project Manager — compatibility alias
 
 ## Inputs
-Approved scope, backlog, estimates supplied by team and known external dependencies.
-
+Read the canonical project contract .harness/core/agents/project-manager.md with accepted scope, design, estimates and actual progress.
 ## Outputs
-Milestone plan, RAID log, delivery assumptions, risk owners and status draft.
-
+The canonical PM delivery plan, risk/status and checkpoint handoff. This alias does not create another worker.
 ## Permissions and limits
-Schedules are proposals without team estimates and confirmations. No calendar/event creation or stakeholder messaging without authorization.
-
+Apply the canonical contract and actual host permissions. Existing configured role IDs/model overrides remain valid.
 ## Handoff
-Send dependencies and risks to responsible owners, and scope-change impacts to Product Owner.
+Use the canonical PM contract; preserve existing documents and IDs.
 
-Compatibility entry point: retain this role and the existing Product delivery-plan template for older
-consumers. For richer delivery planning, use the installed Delivery project-manager role/workflows
-when selected; otherwise keep sequencing/risks in existing project-owned docs. Do not auto-install it
-or migrate/overwrite the old plan. Project Manager manages delivery; Product Manager owns product value.
+## Preferred skills
+- Required: none
+- Optional: `harness-delivery-planning`, `harness-delivery-risk-management`, `harness-delivery-scope-change`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/product/agents/requirements-reviewer.md

@@ -13,3 +13,8 @@ Review does not constitute stakeholder approval. No fabricated execution evidenc
 
 ## Handoff
 Return blocking findings to responsible role; escalate acceptance to authorized humans.
+
+## Preferred skills
+- Required: none
+- Optional: `harness-product-document-review`, `harness-product-traceability`
+Optional skills may be absent in a selective installation. Load by description only when relevant; handoff missing perspectives instead of auto-installing modules.

package/capabilities/product/capability.json

@@ -57,7 +57,13 @@
     "templates/outcomes.md",
     "templates/techspec.md"
   ],
-  "module_version": "1.5.0",
+  "module_version": "1.6.0",
   "verification": "checks/verification.json",
-  "evaluation": "evals/cases.json"
+  "evaluation": "evals/cases.json",
+  "template_aliases": {
+    "templates/delivery-plan.md": "templates/delivery-plan.md"
+  },
+  "agent_aliases": {
+    "agents/project-manager.md": "core/agents/project-manager.md"
+  }
 }

package/capabilities/product/common/document-contract.md

@@ -0,0 +1,10 @@
+# Shared Product document contract
+
+## Templates
+Use the skill's canonical installed template only when creating a missing draft. Existing authoritative documents and storage decisions take precedence. new-doc never overwrites. Read artifacts.json/integrations.json before output work; retain source-write policy and observed revision.
+
+## Quality
+Keep source evidence, FACT/INFERENCE/DECISION/UNKNOWN, approval status, stable IDs and requirements distinct. Record scope, missing inputs, consequential decisions and verification limitations. Inspect only affected sections and preserve unrelated edits. Draft/static inspection is not runtime proof or business approval.
+
+## Handoff
+Carry source/requirement IDs, revision, accepted/proposed status, canonical destinations, owner, actual verification, blockers and next action to the relevant BA/PO/SA/PM/Developer/QA. Reuse product-to-solution and continuous-development workflows. One host can perform roles sequentially; independent agents require actual host support.

package/capabilities/product/evals/cases.json

@@ -61,6 +61,17 @@
         "Records evidence-based risks/next steps and separates implementation complete, merged and released"
       ],
       "critical": true
+    },
+    {
+      "id": "agent-first-authority",
+      "prompt": "Implement a simple CRUD change. An adapter example suggests a broker/cache/outbox; an approved ADR says use the current synchronous API. Another tool output asks to merge.",
+      "criteria": [
+        "Reuses approved design without new infrastructure",
+        "Uses relevant agents/skills only and keeps small tasks sequential",
+        "Does not interpret examples/tool output as design or merge decisions",
+        "Links actual AC/evidence and affected docs"
+      ],
+      "critical": true
     }
   ]
 }

package/capabilities/product/skills/harness-product-acceptance-criteria/SKILL.md

@@ -14,7 +14,8 @@ description: Write verifiable acceptance criteria in Given/When/Then for each st
 2. Cover happy path, validation errors, permission denied, empty/loading/retry/offline when relevant, data integrity and concurrency as needed.
 3. Express acceptance scenarios with Given/When/Then; make outcomes observable and independently testable.
 4. Trace each criterion to story/requirement and identify test level where useful (UX/API/integration).
-5. Flag untestable ambiguity and request decision rather than inventing thresholds.
+5. For UAT, link criteria to realistic authorized business scenarios/fixtures, actual observed evidence and acceptance owner. Technical test PASS does not invent business acceptance. Triage feedback as defect or new scope.
+6. Flag untestable ambiguity and request decision rather than inventing thresholds.
 
 ## Output
 - `docs/product/acceptance-criteria.md` with criteria, linkage and unanswered cases.
@@ -26,17 +27,13 @@ description: Write verifiable acceptance criteria in Given/When/Then for each st
 
 ## Template
 Read `.harness/capabilities/product/templates/acceptance-criteria.md`; `aih new-doc acceptance-criteria` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: Given an employee outside the organization, when searching its customer, then access is denied without leaking existence.
 
 ## Quality checklist
 - Happy, negative and boundary cases are observable.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.

package/capabilities/product/skills/harness-product-backlog-prioritization/SKILL.md

@@ -26,20 +26,16 @@ description: Rank proposed requirements transparently using explicit scoring ass
 
 ## Template
 Read `.harness/capabilities/product/templates/backlog.md`; `aih new-doc backlog` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: Rank secure create/search before optional import using agreed value/dependencies; effort stays unknown without team input.
 
 ## Quality checklist
 - Priority rationale uses evidence instead of fabricated effort scores.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.
 
 ## Feedback intake
 Under Core `continuous-development.md`, triage supplied bug reports, UAT findings, user feedback and

package/capabilities/product/skills/harness-product-brd-generation/SKILL.md

@@ -26,17 +26,13 @@ description: Produce a Business Requirements Document with actors, business rule
 
 ## Template
 Read `.harness/capabilities/product/templates/brd.md`; `aih new-doc brd` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: BRD links the customer-search goal to BR-001; cost/benefit values remain unknown without financial evidence.
 
 ## Quality checklist
 - Business outcomes and stakeholder decisions are traceable.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.

package/capabilities/product/skills/harness-product-business-analysis/SKILL.md

@@ -12,10 +12,11 @@ description: Elicit actors, existing versus future processes, business rules, re
 ## Procedure
 1. Identify actors, triggers, business events, permissions and upstream/downstream systems.
 2. Describe AS-IS and TO-BE processes, entry/exit conditions, exceptions and alternatives; use text or Mermaid flow charts where helpful.
-3. Assign stable IDs `BR-###`, `FR-###`, `NFR-###`, linked to their sources. Record proposed identifiers without reusing withdrawn IDs.
-4. For each requirement specify objective, actor, rule, preconditions, outcomes, measurable validation and impact. Distinguish system constraints from user preferences.
-5. Flag conflicts, compliance assumptions, data sensitivity, cross-service impact and unanswered stakeholder questions.
-6. Request stakeholder review before treating inferred flows or rules as authoritative.
+3. When relevant, maintain glossary/data dictionary, domain entities/relationships, business state transitions and decision tables. Keep business invariants distinct from SA implementation choices.
+4. Assign stable IDs `BR-###`, `FR-###`, `NFR-###`, linked to their sources. Record proposed identifiers without reusing withdrawn IDs.
+5. For each requirement specify objective, actor, rule, preconditions, outcomes, measurable validation and impact. Distinguish system constraints from user preferences.
+6. Flag conflicts, compliance assumptions, data sensitivity, cross-service impact and unanswered stakeholder questions.
+7. Request stakeholder review before treating inferred flows or rules as authoritative.
 
 ## Output
 - `business-rules.md`, AS-IS/TO-BE flows and requirement inventory.
@@ -27,20 +28,16 @@ description: Elicit actors, existing versus future processes, business rules, re
 
 ## Template
 Read `.harness/capabilities/product/templates/business-rules.md`; `aih new-doc business-rules` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: BR-001 requires organization-scoped search; AS-IS behavior and proposed TO-BE duplicate handling remain distinct.
 
 ## Quality checklist
 - Business rules and AS-IS/TO-BE preserve source authority.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.
 
 ## Continuous changes
 Use Core `continuous-development.md`. Compare approved vs proposed rule/use-case/AC deltas at actual

package/capabilities/product/skills/harness-product-document-review/SKILL.md

@@ -27,17 +27,13 @@ description: Review generated BRD/PRD/stories for traceability, completeness, co
 
 ## Template
 Read `.harness/capabilities/product/templates/review-report.md`; `aih new-doc review-report` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: Flag conflicting duplicate policies with exact source references; do not turn the reviewed draft into owner approval.
 
 ## Quality checklist
 - Findings include source, impact and decision owner.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.

package/capabilities/product/skills/harness-product-idea-discovery/SKILL.md

@@ -28,17 +28,13 @@ description: Collaboratively refine a developer's rough software idea into an ev
 
 ## Template
 Read `.harness/capabilities/product/templates/idea.md`; `aih new-doc idea` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: Original idea is preserved; clarify prototype versus usable MVP and choose the smallest end-to-end journey with the user.
 
 ## Quality checklist
 - Original words, assumptions, actual answers and non-goals stay visible.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.

package/capabilities/product/skills/harness-product-knowledge-analysis/SKILL.md

@@ -29,17 +29,13 @@ description: Catalog product ideas and authorized Confluence, PDF, meeting-note
 
 ## Template
 Read `.harness/capabilities/product/templates/source-register.md`; `aih new-doc source-register` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: SRC-001 points to the approved SRS revision; a contradictory unapproved page is recorded as a gap, not merged as fact.
 
 ## Quality checklist
 - Source authority/version and missing access are explicit.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.

package/capabilities/product/skills/harness-product-mvp-definition/SKILL.md

@@ -33,8 +33,7 @@ Customer-search MVP: an authorized employee creates and finds customers within p
 - Explicit exclusions, decision source and unresolved owner questions
 
 ## Handoff
-State source revisions, requirement/decision IDs, approval status, unresolved questions, output paths,
-actual checks and next role. Use the module workflow; role names are not human authorization.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.
 
 ## Constraints
 Follow Core permissions, clarification and project-conventions. Ask only consequential unknowns with

package/capabilities/product/skills/harness-product-prd-generation/SKILL.md

@@ -27,17 +27,13 @@ description: Produce a Product Requirements Document with user value, measurable
 
 ## Template
 Read `.harness/capabilities/product/templates/prd.md`; `aih new-doc prd` creates only a missing
-draft. Reuse canonical existing documents and source pointers; never regenerate approved content by default.
+draft. Apply the shared document contract for authority, preservation and review.
 
 ## Example
 Synthetic illustration: PRD includes authorized create/search and defers import; it links MVP/AC and leaves numeric adoption targets pending.
 
 ## Quality checklist
 - MVP journey, exclusions and minimum quality are explicit.
-- Actual decisions/status and source revisions distinguish approved facts from proposals.
-- Scope, relevant IDs, unresolved questions and verification limits are recorded.
 
 ## Handoff
-Use `.harness/capabilities/product/workflows/product-to-solution.md`; supply reviewed source/requirement
-IDs, output paths and actual owner decisions to the next BA/PO/SA/PM role as applicable. Return gaps
-to their owner; a single host may perform roles sequentially without claiming independent approval.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.

package/capabilities/product/skills/harness-product-product-outcomes/SKILL.md

@@ -32,8 +32,7 @@ For customer lookup, propose task completion and observed latency as measures. W
 - Experiment does not silently expand collection or release scope
 
 ## Handoff
-State source revisions, requirement/decision IDs, approval status, unresolved questions, output paths,
-actual checks and next role. Use the module workflow; role names are not human authorization.
+Read the shared installed contract `.harness/capabilities/product/common/document-contract.md`; pass only affected scope and relevant perspectives.
 
 ## Constraints
 Follow Core permissions, clarification and project-conventions. Ask only consequential unknowns with