@geraldmaron/construct 1.0.15 → 1.0.17

package/skills/ai/orchestration-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: ai-orchestration-workflow
 description: Use this skill when the request involves agent orchestration, phase transitions, task keys, handoff quality, workflow state, or project alignment.
+inputs: [agent-spec, workflow-state]
+artifactType: guidance
 ---
 # Construct Orchestration Workflow
 

package/skills/ai/prompt-and-eval.md

@@ -1,6 +1,8 @@
 ---
 name: ai-prompt-and-eval
 description: Use this skill when designing prompts, evaluating model performance, or optimizing LLM behavior.
+inputs: [prompt, eval-dataset, model-output]
+artifactType: eval-report
 ---
 # Prompt Engineering and Evaluation
 

package/skills/ai/prompt-optimizer.md

@@ -1,6 +1,8 @@
 ---
 name: ai-prompt-optimizer
 description: Closed-loop prompt auto-optimization guide. Use when the task matches the trigger conditions described in the body.
+inputs: [prompt, model-output, eval-dataset]
+artifactType: prompt
 ---
 # Prompt Auto-Optimization Loop
 

package/skills/ai/rag-system.md

@@ -1,6 +1,8 @@
 ---
 name: ai-rag-system
 description: Use this skill when building retrieval-augmented generation pipelines, vector search, or knowledge-grounded AI systems.
+inputs: [eval-dataset, prompt]
+artifactType: guidance
 ---
 # RAG System Design
 

package/skills/ai/trace-triage.md

@@ -0,0 +1,36 @@
+---
+name: ai-trace-triage
+description: "Use when: agent telemetry traces need triage to find where a run went wrong — the failing step, the cause category, and whether it is a regression or a one-off."
+inputs: [telemetry-traces]
+artifactType: trace-findings
+---
+# Trace Triage
+
+Use this skill when agent telemetry traces need to be triaged to locate failures and separate systemic regressions from one-off noise.
+
+A stable median score hides high-variance agents failing silently. Triage works the tail and the deltas, not the average.
+
+## Steps
+
+1. **Frame the window and baseline.** Compare the current window against a prior baseline of the same agents/skills; an absolute score means little without the delta.
+2. **Sort by the tail, not the mean.** Surface the worst p10 runs and the largest score drops since baseline — that is where real failures live.
+3. **For each failing run, locate the failing step**: which role/tool call produced the bad output or error. Read the span, not just the verdict.
+4. **Classify the cause**: prompt/instruction gap, wrong model tier, missing context/evidence, tool error, or genuine task ambiguity. Do not default to "prompt issue".
+5. **Regression vs one-off**: does the same failure recur across runs (systemic) or appear once (noise)? Only systemic failures warrant a fix; flag one-offs for watch.
+6. **Hand off** systemic findings with the trace id, the failing span, the cause class, and a proposed direction (to prompt-optimizer, engineer, or evaluator).
+
+## Output shape
+
+```
+## Window: <range> vs baseline <range>
+| traceId | agent/skill | failing step | cause class | regression? | Δ score |
+|---|---|---|---|---|---|
+
+## Systemic (fix) vs one-off (watch)
+```
+
+## Verification bar
+
+- Every finding cites a real traceId and the specific span that failed.
+- Regression claims are backed by recurrence across runs, not a single bad sample.
+- Cause classification is evidence-based; "unclear" is a valid class when the trace doesn't show why.

package/skills/architecture/api-design.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-api-design
 description: Use this skill when designing REST, GraphQL, or gRPC APIs.
+inputs: [system-design, requirements]
+artifactType: api-design
 ---
 # API Design
 

package/skills/architecture/caching.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-caching
 description: Use this skill when designing caching strategies for applications, APIs, or infrastructure.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Caching
 

package/skills/architecture/cloud-native.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-cloud-native
 description: Use this skill when designing containerized, orchestrated, or microservice-based systems.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Cloud-Native Architecture
 

package/skills/architecture/message-queue.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-message-queue
 description: Use this skill when designing asynchronous communication, event-driven systems, or message-based integrations.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Message Queues and Event-Driven Architecture
 

package/skills/architecture/security-arch.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-security-arch
 description: Use this skill when designing authentication, authorization, network security, or zero-trust architectures.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Security Architecture
 

package/skills/compliance/ai-disclosure.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-ai-disclosure
 description: Use this skill when reviewing AI features for disclosure requirements, transparency obligations, or emerging AI regulation compliance.
+inputs: [artifact, data-flow]
+artifactType: privacy-assessment
 ---
 # AI Disclosure
 

package/skills/compliance/data-privacy.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-data-privacy
 description: Use this skill when reviewing data collection, storage, processing, or retention for privacy regulation compliance.
+inputs: [data-flow, artifact]
+artifactType: privacy-assessment
 ---
 # Data Privacy
 

package/skills/compliance/license-audit.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-license-audit
 description: Use this skill when auditing dependency licenses, evaluating OSS compliance risk, or preparing license inventories for legal review.
+inputs: [dependency-manifest]
+artifactType: license-report
 ---
 # License Audit
 

package/skills/compliance/regulatory-review.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-regulatory-review
 description: Use this skill when conducting a compliance review before shipping features that handle user data, financial transactions, AI decisions, or regulated content.
+inputs: [artifact, data-flow, dependency-manifest]
+artifactType: compliance-review
 ---
 # Regulatory Review
 

package/skills/development/cpp.md

@@ -1,6 +1,8 @@
 ---
 name: development-cpp
 description: Use this skill when writing, reviewing, or debugging C or C++ code.
+inputs: [code, repo]
+artifactType: code
 ---
 # C/C++ Best Practices
 

package/skills/development/go.md

@@ -1,6 +1,8 @@
 ---
 name: development-go
 description: Use this skill when writing, reviewing, or debugging Go code.
+inputs: [code, repo]
+artifactType: code
 ---
 # Go Best Practices
 

package/skills/development/java.md

@@ -1,6 +1,8 @@
 ---
 name: development-java
 description: Use this skill when writing, reviewing, or debugging Java or Kotlin code on the JVM.
+inputs: [code, repo]
+artifactType: code
 ---
 # Java Best Practices
 

package/skills/development/kotlin.md

@@ -1,6 +1,8 @@
 ---
 name: development-kotlin
 description: Patterns, anti-patterns, and reference guidance for Kotlin / Android Development. Use when the task involves kotlin / android development.
+inputs: [code, repo]
+artifactType: code
 ---
 # Kotlin / Android Development
 

package/skills/development/mobile-crossplatform.md

@@ -1,6 +1,8 @@
 ---
 name: development-mobile-crossplatform
 description: Before choosing a framework, answer:. Use when the task matches the trigger conditions described in the body.
+inputs: [requirements, code]
+artifactType: guidance
 ---
 # Mobile Cross-Platform Development
 

package/skills/development/python.md

@@ -1,6 +1,8 @@
 ---
 name: development-python
 description: Use this skill when writing, reviewing, or debugging Python code.
+inputs: [code, repo]
+artifactType: code
 ---
 # Python Best Practices
 

package/skills/development/rust.md

@@ -1,6 +1,8 @@
 ---
 name: development-rust
 description: Use this skill when writing, reviewing, or debugging Rust code.
+inputs: [code, repo]
+artifactType: code
 ---
 # Rust Best Practices
 

package/skills/development/shell.md

@@ -1,6 +1,8 @@
 ---
 name: development-shell
 description: Use this skill when writing, reviewing, or debugging Bash, Zsh, or POSIX shell scripts.
+inputs: [code, repo]
+artifactType: code
 ---
 # Shell Scripting Best Practices
 

package/skills/development/swift.md

@@ -1,6 +1,8 @@
 ---
 name: development-swift
 description: Swift 6 enforces data-race safety at compile time. Annotate isolation boundary explicitly:. Use when the task matches the trigger conditions described in the body.
+inputs: [code, repo]
+artifactType: code
 ---
 # Swift / iOS Development
 

package/skills/development/typescript.md

@@ -1,6 +1,8 @@
 ---
 name: development-typescript
 description: Use this skill when writing, reviewing, or debugging TypeScript or JavaScript code.
+inputs: [code, repo]
+artifactType: code
 ---
 # TypeScript Best Practices
 

package/skills/devops/ci-cd.md

@@ -1,6 +1,8 @@
 ---
 name: devops-ci-cd
 description: Use this skill when designing, debugging, or optimizing CI/CD pipelines.
+inputs: [pipeline-config, repo]
+artifactType: ci-pipeline
 ---
 # CI/CD
 

package/skills/devops/containerization.md

@@ -1,6 +1,8 @@
 ---
 name: devops-containerization
 description: Use this skill when writing Dockerfiles, optimizing image size, or securing container builds.
+inputs: [service, repo]
+artifactType: dockerfile
 ---
 # Containerization
 

package/skills/devops/cost-optimization.md

@@ -1,6 +1,8 @@
 ---
 name: devops-cost-optimization
 description: Use this skill when reducing cloud spend, right-sizing resources, or implementing FinOps practices.
+inputs: [service, cost-data]
+artifactType: cost-optimization-plan
 ---
 # Cloud Cost Optimization
 

package/skills/devops/data-engineering.md

@@ -1,6 +1,8 @@
 ---
 name: devops-data-engineering
 description: "1. **Idempotency**: pipelines can run multiple times without duplicating data 2. **Observability**: every pipeline run logs row counts, latency, and anomalies 3. **Data contracts**: producers and consumers agree on schema and SLAs 4. **Lineage**: know where every column came from and what it feeds. Use when the task matches the trigger conditions described in the body."
+inputs: [pipeline-config, data-contract]
+artifactType: data-pipeline
 ---
 # Data Engineering
 

package/skills/devops/database.md

@@ -1,6 +1,8 @@
 ---
 name: devops-database
 description: Use this skill when designing schemas, writing migrations, optimizing queries, or selecting databases.
+inputs: [schema, query]
+artifactType: schema-design
 ---
 # Database Patterns
 

package/skills/devops/dependency-management.md

@@ -1,6 +1,8 @@
 ---
 name: devops-dependency-management
 description: Use this skill when managing package upgrades, resolving CVEs, or establishing lock file and versioning policy.
+inputs: [dependency-manifest, repo]
+artifactType: dependency-report
 ---
 # Dependency Management
 

package/skills/devops/devsecops.md

@@ -1,6 +1,8 @@
 ---
 name: devops-devsecops
 description: Use this skill when integrating security into CI/CD pipelines, managing supply chain risk, or automating security scanning.
+inputs: [pipeline-config, service]
+artifactType: security-plan
 ---
 # DevSecOps
 

package/skills/devops/git-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: devops-git-workflow
 description: Use this skill when establishing branching strategies, commit conventions, or code integration practices.
+inputs: [repo, task-context]
+artifactType: guidance
 ---
 # Git Workflow
 

package/skills/devops/incident-response.md

@@ -1,6 +1,8 @@
 ---
 name: devops-incident-response
 description: "Define severity in your runbook and assign it early: it determines escalation and comms cadence. Use when the task matches the trigger conditions described in the body."
+inputs: [incident, alert]
+artifactType: incident-runbook
 ---
 # Incident Response
 

package/skills/devops/monorepo.md

@@ -1,6 +1,8 @@
 ---
 name: devops-monorepo
 description: Use this skill when selecting monorepo tooling, structuring packages, or optimizing affected-only builds.
+inputs: [repo, pipeline-config]
+artifactType: guidance
 ---
 # Monorepo
 

package/skills/devops/observability.md

@@ -1,6 +1,8 @@
 ---
 name: devops-observability
 description: Use this skill when designing logging, tracing, metrics, or alerting systems.
+inputs: [service, metrics]
+artifactType: observability-plan
 ---
 # Observability
 

package/skills/devops/performance.md

@@ -1,6 +1,8 @@
 ---
 name: devops-performance
 description: Use this skill when profiling, load testing, or optimizing application and infrastructure performance.
+inputs: [service, metrics]
+artifactType: performance-plan
 ---
 # Performance Engineering
 

package/skills/devops/testing.md

@@ -1,6 +1,8 @@
 ---
 name: devops-testing
 description: Use this skill when planning test coverage, selecting test types, or establishing testing practices.
+inputs: [repo, task-context]
+artifactType: test-plan
 ---
 # Testing Strategy
 

package/skills/docs/adr-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-adr-workflow
 description: "Use when: an architectural decision is made that affects the system structure, data model, API contracts, or technology choices."
+inputs: [decision-context]
+artifactType: adr
 ---
 # ADR Workflow
 

package/skills/docs/backlog-proposal-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-backlog-proposal-workflow
 description: "Use when: product evidence should create or update Jira, Linear, GitHub Issues, or another tracker."
+inputs: [evidence-brief, prd, signal]
+artifactType: backlog-proposal
 ---
 # Backlog Proposal Workflow
 

package/skills/docs/customer-profile-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-customer-profile-workflow
 description: "Use when: customer evidence should update durable product memory."
+inputs: [signal, customer-profile]
+artifactType: customer-profile
 ---
 # Customer Profile Workflow
 

package/skills/docs/document-ingest-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-document-ingest-workflow
 description: "Use when: the user points at a PDF, Word doc, spreadsheet, slide deck, export, or mixed document folder and wants a markdown version that Construct can search efficiently later."
+inputs: [document]
+artifactType: ingested-markdown
 ---
 # Document Ingest Workflow
 

package/skills/docs/evidence-ingest-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-evidence-ingest-workflow
 description: "Use when: the user pastes customer notes, Slack threads, support tickets, sales notes, research snippets, RFCs, analytics summaries, or competitor signals."
+inputs: [signal, document]
+artifactType: evidence-brief
 ---
 # Evidence Ingest Workflow
 

package/skills/docs/init-docs.md

@@ -1,6 +1,8 @@
 ---
 name: docs-init-docs
 description: "`init docs`, `create docs structure`, `set up documentation`, `docs scaffold`, `documentation init`. Use when the task matches the trigger conditions described in the body."
+inputs: [task-context]
+artifactType: docs-scaffold
 ---
 # Skill: init-docs: Initialize Project Documentation Structure
 

package/skills/docs/init-project.md

@@ -1,6 +1,8 @@
 ---
 name: docs-init-project
 description: "Use when: starting work on a new project or joining an existing one without doc structure."
+inputs: [repo]
+artifactType: docs-scaffold
 ---
 # Project Initialization
 

package/skills/docs/memo-and-decision-capture.md

@@ -0,0 +1,45 @@
+---
+name: docs-memo-and-decision-capture
+description: "Use when: a decision, status update, or announcement needs to be captured as a short, durable memo that states the decision, its rationale, and what changes."
+inputs: [decision-context]
+artifactType: memo
+---
+# Memo & Decision Capture
+
+Use this skill when a decision, status update, or announcement needs to be captured as a short, durable memo.
+
+A good memo is short and load-bearing: a reader six months later should understand what was decided, why, and what it changed — without attending the meeting. Length is not value; a memo that buries the decision under context has failed.
+
+## Steps
+
+1. **Lead with the decision or update** in the first sentence. The reader should not have to hunt for it.
+2. **State the context** in 2–4 sentences: what prompted this, what problem it addresses.
+3. **Record the rationale** — why this option over the alternatives actually considered. If alternatives were weighed, name them and why they lost.
+4. **State what changes** as a result: who does what differently, what is now in or out of scope.
+5. **List action items** with owners, if any.
+6. **Date and attribute** the memo. A memo without a date is not durable.
+
+## Output shape
+
+```
+# Memo: <subject>
+_<date> · <author>_
+
+**Decision/Update:** <one sentence>
+
+## Context
+<2–4 sentences>
+
+## Rationale
+<why this, over what alternatives>
+
+## What changes
+- <change> — owner: <name>
+```
+
+## Verification bar
+
+- The decision/update is stated in the first sentence, unhedged where the decision is firm.
+- Rationale references only alternatives actually considered — no invented options.
+- The memo is dated and attributed.
+- Nothing load-bearing is asserted that the source context does not support; unknowns are written as `unknown`.

package/skills/docs/prd-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-prd-workflow
 description: "Use when: the user asks to create a PRD, platform spec, business case, RFC, or requirements document."
+inputs: [research-question, evidence-brief]
+artifactType: prd
 ---
 # PRD Workflow
 

package/skills/docs/prfaq-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-prfaq-workflow
 description: "Use when: the user asks for a PRFAQ, working-backwards doc, launch narrative, or FAQ grounded in product evidence."
+inputs: [prd, evidence-brief]
+artifactType: prfaq
 ---
 # PRFAQ Workflow
 

package/skills/docs/product-intelligence-review.md

@@ -1,6 +1,8 @@
 ---
 name: docs-product-intelligence-review
 description: "Use when: reviewing PRDs, Meta PRDs, PRFAQs, evidence briefs, signal briefs, customer profiles, or backlog proposals."
+inputs: [prd, evidence-brief]
+artifactType: review
 ---
 # Product Intelligence Review
 

package/skills/docs/product-intelligence-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-product-intelligence-workflow
 description: "Use when: the request involves customer evidence, PM synthesis, product requirements, PRDs, PRFAQs, customer profiles, product signals, or backlog proposals."
+inputs: [signal, evidence-brief]
+artifactType: prd
 ---
 # Product Intelligence Workflow
 

package/skills/docs/product-signal-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-product-signal-workflow
 description: "Use when: the user asks what customers are asking for, what themes are emerging, whether evidence is strong enough, or what should become a PRD."
+inputs: [signal, evidence-brief]
+artifactType: signal-brief
 ---
 # Product Signal Workflow
 

package/skills/docs/research-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-research-workflow
 description: "Use when: the user asks to research a topic, investigate a question, or gather evidence for a decision."
+inputs: [research-question]
+artifactType: research-brief
 ---
 # Research Workflow
 

package/skills/docs/runbook-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-runbook-workflow
 description: "Use when: creating operational procedures for services, alerts, or recurring operations."
+inputs: [service, incident]
+artifactType: runbook
 ---
 # Runbook Workflow
 

package/skills/docs/strategy-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: docs-strategy-workflow
 description: "Use when: the user asks about product direction, strategic bets, what to prioritize, whether a signal aligns with strategy, or wants to update the strategy."
+inputs: [signal, decision-context]
+artifactType: strategy
 ---
 # Strategy Workflow
 

package/skills/docs/transcript-synthesis.md

@@ -0,0 +1,43 @@
+---
+name: docs-transcript-synthesis
+description: "Use when: a meeting, call, or interview transcript needs to be turned into a summary, the decisions made, and concrete action items with owners."
+inputs: [transcript-text]
+artifactType: meeting-summary
+---
+# Transcript Synthesis
+
+Use this skill when a meeting, call, or interview transcript needs to be turned into a structured summary with decisions and action items.
+
+A raw transcript is a low-signal artifact: speaker turns, filler, and tangents bury the few load-bearing outcomes. The job is to extract those outcomes faithfully without inventing any that were not actually stated.
+
+## Steps
+
+1. **Read the whole transcript first.** Do not summarize incrementally — a decision late in the call often reverses an earlier one.
+2. **Identify participants and roles** if stated. Note who owns what. If unstated, write `owner: unassigned` rather than guessing.
+3. **Extract decisions.** A decision is an explicit commitment ("we'll ship X", "we're not doing Y"). Quote or tightly paraphrase the line that establishes it. Do not promote a musing ("maybe we could…") to a decision.
+4. **Extract action items** as `{ action, owner, due? }`. Only include items someone actually committed to. Mark `due` only if a date was stated.
+5. **Extract open questions** — anything raised and left unresolved.
+6. **Write a 3–6 sentence summary** of what the conversation was about and what changed as a result.
+7. **Flag low-confidence sections** — crosstalk, inaudible markers, ambiguous antecedents — as `[unclear]` rather than smoothing them over.
+
+## Output shape
+
+```
+## Summary
+<3–6 sentences>
+
+## Decisions
+- <decision> — basis: "<quoted/paraphrased line>"
+
+## Action items
+- [ ] <action> — owner: <name|unassigned>[, due: <date>]
+
+## Open questions
+- <question>
+```
+
+## Verification bar
+
+- Every decision and action item traces to an actual statement in the transcript — no invented commitments or owners.
+- Tentative language stays tentative; do not sharpen "maybe" into "will".
+- Unresolved or inaudible content is surfaced, not silently dropped.

package/skills/exploration/dependency-graph-reading.md

@@ -1,6 +1,8 @@
 ---
 name: exploration-dependency-graph-reading
 description: Use when assessing the risk surface of a project's dependencies, planning upgrades, or evaluating a new codebase's supply chain posture.
+inputs: [dependency-manifest, repo]
+artifactType: dependency-graph
 ---
 # Dependency Graph Reading