@geraldmaron/construct 1.0.0

package/templates/docs/runbook.md

@@ -0,0 +1,33 @@
+# Runbook: {service or alert name}
+
+- **Service**: {service}
+- **Owner**: {team or on-call rotation}
+- **Last tested**: {YYYY-MM-DD}
+- **Severity**: SEV-1 | SEV-2 | SEV-3
+
+## Alert trigger
+<!-- The exact alert, log pattern, or user report that brings someone to this page. Include the query or alert rule. -->
+
+## Symptoms
+<!-- What an operator will observe. Dashboards, error rates, user-visible behavior. -->
+
+## Impact
+<!-- Who is affected and how badly. Data loss? Degraded performance? Complete outage? -->
+
+## Diagnostic steps
+<!-- Ordered checks from cheapest to most expensive. Each step: what to check, how to check it, what the answer means. -->
+
+## Remediation
+<!-- The fix. Step-by-step, with exact commands or UI paths. Include expected output for each step. -->
+
+## Rollback
+<!-- How to undo the remediation if it makes things worse. Tested? Include the last test date. -->
+
+## Escalation
+<!-- Who to page, in what order, after how long. Include paths for both technical and business escalation. -->
+
+## Post-incident
+<!-- What to capture for the incident report. Pointers to logs, dashboards, trace IDs to preserve. -->
+
+## References
+<!-- Architecture docs, related runbooks, past incidents. -->

package/templates/docs/signal-brief.md

@@ -0,0 +1,25 @@
+# Signal Brief: {title}
+
+- **Date**: {YYYY-MM-DD}
+- **Owner**: {name}
+- **Signal strength**: weak | emerging | strong
+
+<!--
+Use when evidence is real but not strong enough for a PRD. Preserve the signal
+without pretending the requirements are ready.
+-->
+
+## Signal
+<!-- One or two paragraphs. What appears to be happening, and where the signal came from. -->
+
+## Evidence
+<!-- Cite the concrete notes, tickets, customer quotes, traces, or analytics that support the signal. -->
+
+## Why it matters
+<!-- What product, customer, or business decision this could affect if the signal strengthens. -->
+
+## What would make this actionable
+<!-- The evidence threshold needed to promote this into an evidence brief, PRD, backlog proposal, or research task. -->
+
+## Follow-up
+<!-- Owner, next evidence to gather, and review date. -->