@geraldmaron/construct 1.0.15 → 1.0.17

package/skills/roles/orchestrator.md

@@ -1,6 +1,8 @@
 ---
 name: roles-orchestrator
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Orchestrator role. Use when reviewing or generating work by cx-orchestrator, or when an agent is acting in the Orchestrator role.
+inputs: [task-context, request]
+artifactType: role-guidance
 role: orchestrator
 applies_to:
   - cx-orchestrator

package/skills/roles/product-manager.ai-product.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager-ai-product
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager — AI Product role. Use when reviewing or generating work by cx-product-manager, or when an agent is acting in the Product Manager — AI Product role.
+inputs: [prd, eval-criteria]
+artifactType: role-guidance
 role: product-manager.ai-product
 applies_to:
   - cx-product-manager

package/skills/roles/product-manager.business-strategy.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager-business-strategy
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager — Business Strategy role. Use when reviewing or generating work by cx-business-strategist, or when an agent is acting in the Product Manager — Business Strategy role.
+inputs: [strategy-doc, competitive-analysis]
+artifactType: guidance
 role: product-manager.business-strategy
 applies_to:
   - cx-business-strategist

package/skills/roles/product-manager.enterprise.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager-enterprise
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager — Enterprise role. Use when reviewing or generating work by cx-product-manager, or when an agent is acting in the Product Manager — Enterprise role.
+inputs: [prd, task-context]
+artifactType: guidance
 role: product-manager.enterprise
 applies_to:
   - cx-product-manager

package/skills/roles/product-manager.growth.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager-growth
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager — Growth role. Use when reviewing or generating work by cx-product-manager, cx-business-strategist, or when an agent is acting in the Product Manager — Growth role.
+inputs: [prd, growth-metrics]
+artifactType: guidance
 role: product-manager.growth
 applies_to:
   - cx-product-manager

package/skills/roles/product-manager.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager role. Use when reviewing or generating work by cx-product-manager, cx-business-strategist, or when an agent is acting in the Product Manager role.
+inputs: [prd, user-evidence]
+artifactType: guidance
 role: product-manager
 applies_to:
   - cx-product-manager

package/skills/roles/product-manager.platform.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager-platform
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager — Platform role. Use when reviewing or generating work by cx-product-manager, or when an agent is acting in the Product Manager — Platform role.
+inputs: [prd, api-spec]
+artifactType: guidance
 role: product-manager.platform
 applies_to:
   - cx-product-manager

package/skills/roles/product-manager.product.md

@@ -1,6 +1,8 @@
 ---
 name: roles-product-manager-product
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Product Manager — Product role. Use when reviewing or generating work by cx-product-manager, or when an agent is acting in the Product Manager — Product role.
+inputs: [prd, task-context]
+artifactType: guidance
 role: product-manager.product
 applies_to:
   - cx-product-manager

package/skills/roles/qa.ai-eval.md

@@ -1,6 +1,8 @@
 ---
 name: roles-qa-ai-eval
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the QA — AI Eval role. Use when reviewing or generating work by cx-qa, cx-test-automation, cx-evaluator, or when an agent is acting in the QA — AI Eval role.
+inputs: [eval-set, model-output]
+artifactType: guidance
 role: qa.ai-eval
 applies_to:
   - cx-qa

package/skills/roles/qa.api-contract.md

@@ -1,6 +1,8 @@
 ---
 name: roles-qa-api-contract
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the QA — API Contract role. Use when reviewing or generating work by cx-qa, cx-test-automation, or when an agent is acting in the QA — API Contract role.
+inputs: [api-spec, test-suite]
+artifactType: guidance
 role: qa.api-contract
 applies_to:
   - cx-qa

package/skills/roles/qa.data-pipeline.md

@@ -1,6 +1,8 @@
 ---
 name: roles-qa-data-pipeline
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the QA — Data Pipeline role. Use when reviewing or generating work by cx-qa, cx-test-automation, or when an agent is acting in the QA — Data Pipeline role.
+inputs: [pipeline, test-suite]
+artifactType: guidance
 role: qa.data-pipeline
 applies_to:
   - cx-qa

package/skills/roles/qa.md

@@ -1,6 +1,8 @@
 ---
 name: roles-qa
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the QA role. Use when reviewing or generating work by cx-qa, cx-test-automation, or when an agent is acting in the QA role.
+inputs: [test-suite, code-diff]
+artifactType: guidance
 role: qa
 applies_to:
   - cx-qa

package/skills/roles/qa.test-automation.md

@@ -1,6 +1,8 @@
 ---
 name: roles-qa-test-automation
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the QA — Test Automation role. Use when reviewing or generating work by cx-test-automation, or when an agent is acting in the QA — Test Automation role.
+inputs: [test-suite, task-context]
+artifactType: guidance
 role: qa.test-automation
 applies_to:
   - cx-test-automation

package/skills/roles/qa.web-ui.md

@@ -1,6 +1,8 @@
 ---
 name: roles-qa-web-ui
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the QA — Web UI role. Use when reviewing or generating work by cx-qa, cx-test-automation, or when an agent is acting in the QA — Web UI role.
+inputs: [test-suite, ui]
+artifactType: guidance
 role: qa.web-ui
 applies_to:
   - cx-qa

package/skills/roles/researcher.explorer.md

@@ -1,6 +1,8 @@
 ---
 name: roles-researcher-explorer
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Researcher — Explorer role. Use when reviewing or generating work by cx-explorer, or when an agent is acting in the Researcher — Explorer role.
+inputs: [repo, task-context]
+artifactType: guidance
 role: researcher.explorer
 applies_to:
   - cx-explorer

package/skills/roles/researcher.md

@@ -1,6 +1,8 @@
 ---
 name: roles-researcher
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Researcher role. Use when reviewing or generating work by cx-researcher, cx-ux-researcher, cx-explorer, or when an agent is acting in the Researcher role.
+inputs: [research-question, sources]
+artifactType: guidance
 role: researcher
 applies_to:
   - cx-researcher

package/skills/roles/researcher.ux.md

@@ -1,6 +1,8 @@
 ---
 name: roles-researcher-ux
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Researcher — UX role. Use when reviewing or generating work by cx-ux-researcher, or when an agent is acting in the Researcher — UX role.
+inputs: [user-research, interview-data]
+artifactType: guidance
 role: researcher.ux
 applies_to:
   - cx-ux-researcher

package/skills/roles/reviewer.devil-advocate.md

@@ -1,6 +1,8 @@
 ---
 name: roles-reviewer-devil-advocate
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Reviewer — Devil Advocate role. Use when reviewing or generating work by cx-devil-advocate, or when an agent is acting in the Reviewer — Devil Advocate role.
+inputs: [plan, proposal]
+artifactType: guidance
 role: reviewer.devil-advocate
 applies_to:
   - cx-devil-advocate

package/skills/roles/reviewer.evaluator.md

@@ -1,6 +1,8 @@
 ---
 name: roles-reviewer-evaluator
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Reviewer — Evaluator role. Use when reviewing or generating work by cx-evaluator, or when an agent is acting in the Reviewer — Evaluator role.
+inputs: [model-output, eval-set]
+artifactType: guidance
 role: reviewer.evaluator
 applies_to:
   - cx-evaluator

package/skills/roles/reviewer.md

@@ -1,6 +1,8 @@
 ---
 name: roles-reviewer
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Reviewer role. Use when reviewing or generating work by cx-reviewer, cx-devil-advocate, cx-evaluator, cx-trace-reviewer, or when an agent is acting in the Reviewer role.
+inputs: [code-diff, pull-request]
+artifactType: review-report
 role: reviewer
 applies_to:
   - cx-reviewer

package/skills/roles/reviewer.trace.md

@@ -1,6 +1,8 @@
 ---
 name: roles-reviewer-trace
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Reviewer — Trace role. Use when reviewing or generating work by cx-trace-reviewer, or when an agent is acting in the Reviewer — Trace role.
+inputs: [trace, task-context]
+artifactType: guidance
 role: reviewer.trace
 applies_to:
   - cx-trace-reviewer

package/skills/roles/security.ai.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security-ai
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security — AI role. Use when reviewing or generating work by cx-security, cx-ai-engineer, or when an agent is acting in the Security — AI role.
+inputs: [ai-system, task-context]
+artifactType: guidance
 role: security.ai
 applies_to:
   - cx-security

package/skills/roles/security.appsec.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security-appsec
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security — Appsec role. Use when reviewing or generating work by cx-security, or when an agent is acting in the Security — Appsec role.
+inputs: [code-diff, task-context]
+artifactType: guidance
 role: security.appsec
 applies_to:
   - cx-security

package/skills/roles/security.cloud.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security-cloud
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security — Cloud role. Use when reviewing or generating work by cx-security, or when an agent is acting in the Security — Cloud role.
+inputs: [cloud-config, iam-policy]
+artifactType: guidance
 role: security.cloud
 applies_to:
   - cx-security

package/skills/roles/security.legal-compliance.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security-legal-compliance
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security — Legal Compliance role. Use when reviewing or generating work by cx-legal-compliance, or when an agent is acting in the Security — Legal Compliance role.
+inputs: [policy, task-context]
+artifactType: guidance
 role: security.legal-compliance
 applies_to:
   - cx-legal-compliance

package/skills/roles/security.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security role. Use when reviewing or generating work by cx-security, cx-legal-compliance, or when an agent is acting in the Security role.
+inputs: [code-diff, threat-model]
+artifactType: guidance
 role: security
 applies_to:
   - cx-security

package/skills/roles/security.privacy.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security-privacy
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security — Privacy role. Use when reviewing or generating work by cx-security, cx-legal-compliance, or when an agent is acting in the Security — Privacy role.
+inputs: [data-flow, task-context]
+artifactType: guidance
 role: security.privacy
 applies_to:
   - cx-security

package/skills/roles/security.supply-chain.md

@@ -1,6 +1,8 @@
 ---
 name: roles-security-supply-chain
 description: Surfaces anti-patterns, failure modes, and counter-moves specific to the Security — Supply Chain role. Use when reviewing or generating work by cx-security, cx-platform-engineer, or when an agent is acting in the Security — Supply Chain role.
+inputs: [dependencies, ci-config]
+artifactType: guidance
 role: security.supply-chain
 applies_to:
   - cx-security

package/skills/security/blue-team.md

@@ -1,6 +1,8 @@
 ---
 name: security-blue-team
 description: Use this skill when defending systems, responding to incidents, or building detection and monitoring capabilities.
+inputs: [system-design]
+artifactType: guidance
 ---
 # Blue Team
 

package/skills/security/code-audit.md

@@ -1,6 +1,8 @@
 ---
 name: security-code-audit
 description: Use this skill when reviewing source code for security vulnerabilities through static analysis.
+inputs: [code]
+artifactType: vulnerability-report
 ---
 # Code Audit
 

package/skills/security/pentest.md

@@ -1,6 +1,8 @@
 ---
 name: security-pentest
 description: Use this skill when testing web applications or APIs for security vulnerabilities.
+inputs: [system-design, binary]
+artifactType: pentest-report
 ---
 # Penetration Testing
 

package/skills/security/red-team.md

@@ -1,6 +1,8 @@
 ---
 name: security-red-team
 description: Use this skill when planning or executing offensive security assessments, adversary emulation, or attack simulations.
+inputs: [system-design, binary]
+artifactType: pentest-report
 ---
 # Red Team
 

package/skills/security/threat-intel.md

@@ -1,6 +1,8 @@
 ---
 name: security-threat-intel
 description: Use this skill when performing OSINT, threat modeling, or building threat intelligence programs.
+inputs: [system-design]
+artifactType: threat-model
 ---
 # Threat Intelligence
 

package/skills/security/vuln-research.md

@@ -1,6 +1,8 @@
 ---
 name: security-vuln-research
 description: Use this skill when analyzing binaries, fuzzing software, or developing exploits for security research.
+inputs: [target-binary-or-software]
+artifactType: vulnerability-report
 ---
 # Vulnerability Research
 

package/skills/strategy/competitive-landscape.md

@@ -1,6 +1,8 @@
 ---
 name: strategy-competitive-landscape
 description: Use when the team needs a structured read on market positioning before committing direction.
+inputs: [competitor-data, market-signals]
+artifactType: competitive-analysis
 ---
 # Competitive Landscape Analysis
 

package/skills/strategy/jobs-to-be-done.md

@@ -0,0 +1,38 @@
+---
+name: strategy-jobs-to-be-done
+description: "Use when: user research needs to uncover the job a user is hiring a product to do — the underlying progress they seek — rather than feature requests or stated preferences."
+inputs: [user-signals-or-interviews]
+artifactType: jtbd-summary
+---
+# Jobs To Be Done
+
+Use this skill when user research needs to surface the underlying job a user is trying to get done, not the features they ask for.
+
+Users describe solutions ("add a dark mode"); the job is the progress they're trying to make and the context that triggers it. Building to stated features without the job produces local optima nobody hires.
+
+## Steps
+
+1. **Anchor on a real episode**, not a hypothetical. "Tell me about the last time you…" — recent, specific, remembered.
+2. **Trace the timeline**: the trigger (what changed that made them act), the struggle with the current approach, what they tried, and the outcome they were after.
+3. **Separate the job from the solution.** "I want X feature" → ask "what would X let you do that you can't now?" Keep climbing until you reach a stable goal that doesn't reference your product.
+4. **Capture the forces**: push (problems with the status quo), pull (attraction of a new way), and anxieties/habits that hold them back. Adoption is decided by these four forces.
+5. **Watch for non-consumption**: people who have the job but use nothing, or a manual workaround — often the clearest signal of the job.
+6. **State the job** as `When <situation>, I want to <motivation>, so I can <expected outcome>` — sourced to the episodes, not invented.
+
+## Output shape
+
+```
+## Job statement(s)
+- When <situation>, I want to <motivation>, so I can <outcome> — evidence: <episode refs>
+
+## Forces
+- push: … · pull: … · anxiety: … · habit: …
+
+## Non-consumption / workarounds observed
+```
+
+## Verification bar
+
+- Each job statement traces to a specific recounted episode, not a generalization or an assumption about "users".
+- Solution language ("add X") is climbed back to the underlying job, not recorded as the job.
+- Forces and non-consumption come from what was observed/said, labeled where inferred.

package/skills/strategy/market-research-methods.md

@@ -1,6 +1,8 @@
 ---
 name: strategy-market-research-methods
 description: Use when the team needs to validate assumptions before committing resources, or when a decision is being made on vibes rather than signal.
+inputs: [market-signals, user-signals]
+artifactType: market-brief
 ---
 # Market Research Methods
 

package/skills/strategy/narrative-arc.md

@@ -1,6 +1,8 @@
 ---
 name: strategy-narrative-arc
 description: Use when the argument must move people, not just inform them. Strategic narrative is the difference between a document that gets read and one that changes what people do.
+inputs: [market-signals, user-signals]
+artifactType: positioning
 ---
 # Strategic Narrative Construction
 

package/skills/strategy/pricing-positioning.md

@@ -1,6 +1,8 @@
 ---
 name: strategy-pricing-positioning
 description: Use when the team needs to set price, adjust positioning, or defend either to stakeholders.
+inputs: [market-signals, competitor-data]
+artifactType: positioning
 ---
 # Pricing and Positioning
 

package/skills/utility/clean-code.md

@@ -1,6 +1,8 @@
 ---
 name: utility-clean-code
 description: Patterns and heuristics for identifying and removing AI-generated code smells. Use when cleaning up output from AI coding tools.
+inputs: [code]
+artifactType: refactor
 ---
 # AI Slop Removal
 

package/specialists/prompts/cx-engineer.md

@@ -44,7 +44,7 @@ Construct may dispatch you in response to a `handoff.received`, `incident.handof
 **Fence (declared in specialists/role-manifests.json → engineer):**
 - Allowed paths: `lib/**`, `bin/**`, `src/**`, `app/**`, `tests/**`, `docs/**`
 - Allowed bd labels: `bug`, `feature`, `task`, `engineering`, `fix`
-- Approval required: any commit, any push, any edit to protected files (`specialists/registry.json`, `install.sh`, `claude/settings.template.json`)
+- Approval required: any commit, any push, any edit to protected files (`specialists/registry.json`, `lib/setup.mjs`, `claude/settings.template.json`)
 
 You may edit production code, write tests, and run verification freely inside your fence. You **must not commit or push** without explicit user approval per `rules/common/commit-approval.md`. Stage edits, run verification, and stop.
 

package/specialists/registry.json

@@ -50,7 +50,8 @@
       "skills": [
         "ai/orchestration-workflow",
         "operating/orchestration-reference",
-        "operating/change-management"
+        "operating/change-management",
+        "operating/unstructured-triage"
       ],
       "perspective": {
         "bias": "Over-routing to cx-engineer, false simplicity, plans where every task runs in parallel",
@@ -200,7 +201,8 @@
         ]
       },
       "skills": [
-        "docs/research-workflow"
+        "docs/research-workflow",
+        "strategy/jobs-to-be-done"
       ],
       "perspective": {
         "bias": "Ideal-user personas, invisible friction, 'users will figure it out'",
@@ -291,7 +293,8 @@
       },
       "skills": [
         "docs/research-workflow",
-        "devops/dependency-management"
+        "devops/dependency-management",
+        "docs/transcript-synthesis"
       ],
       "perspective": {
         "bias": "Undated sources, version-specific claims without citation, blog posts treated as authoritative",
@@ -389,7 +392,8 @@
       },
       "skills": [
         "devops/observability",
-        "devops/database"
+        "devops/database",
+        "operating/raw-data-structuring"
       ],
       "perspective": {
         "bias": "Vanity metrics, post-hoc success definitions, averages that hide distributions",
@@ -645,7 +649,8 @@
         ]
       },
       "skills": [
-        "quality-gates/review-work"
+        "quality-gates/review-work",
+        "quality-gates/premortem"
       ],
       "perspective": {
         "bias": "Plans that are too elegant, 'unlikely' failure modes, scope drift with stable acceptance criteria",
@@ -1094,7 +1099,8 @@
       "skills": [
         "docs/adr-workflow",
         "docs/runbook-workflow",
-        "docs/init-docs"
+        "docs/init-docs",
+        "docs/memo-and-decision-capture"
       ],
       "perspective": {
         "bias": "Completed work with no context update, decisions 'everyone understands' but nobody wrote down",
@@ -1193,7 +1199,8 @@
         ]
       },
       "skills": [
-        "frontend-design/accessibility"
+        "frontend-design/accessibility",
+        "frontend-design/screen-reader-testing"
       ],
       "perspective": {
         "bias": "ARIA added to pass audits, keyboard navigation never tested, contrast that 'looks fine' but fails the spec",
@@ -1280,7 +1287,8 @@
         ]
       },
       "skills": [
-        "ai/prompt-optimizer"
+        "ai/prompt-optimizer",
+        "ai/trace-triage"
       ],
       "perspective": {
         "bias": "Stable-looking medians hiding variance, trace analyses looking only at successes, promotions on too few traces",
@@ -1322,7 +1330,8 @@
       "skills": [
         "devops/data-engineering",
         "devops/database",
-        "devops/observability"
+        "devops/observability",
+        "operating/raw-data-structuring"
       ],
       "perspective": {
         "bias": "Non-idempotent pipelines, unwritten data contracts, quality gates added after the first corruption incident",

package/specialists/role-manifests.json

@@ -73,7 +73,7 @@
         "allowedPaths": ["lib/**", "bin/**", "src/**", "app/**", "tests/**", "docs/**"],
         "allowedBdLabels": ["bug", "feature", "task", "engineering", "fix"],
         "allowedCommands": ["bd create", "bd note", "bd update", "bd link", "bd label", "bd close", "node", "npm", "git status", "git diff", "git log"],
-        "approvalRequired": ["commit", "push", "edit:specialists/registry.json", "edit:install.sh", "edit:claude/settings.template.json"]
+        "approvalRequired": ["commit", "push", "edit:specialists/registry.json", "edit:lib/setup.mjs", "edit:claude/settings.template.json"]
       },
       "outputs": {
         "bdLabels": ["engineering", "fix"],