// Engineering strategy and technical planning. Builds roadmaps (Now/Next/Later), technology radar, build-vs-buy analyses, and tech debt registers. Trigger when asked about roadmap planning, technology evaluation, build-vs-buy decisions, or tech debt prioritization.
Full environment variable reference for SAM. Use when adding, modifying, or documenting environment variables, configuring deployment, or working with Worker secrets. Trigger when asked about env vars, secrets, or configuration.
Full environment variable reference for SAM. Use when adding, modifying, or documenting environment variables, configuring deployment, or working with Worker secrets.
Content creation from strategy artifacts. Drafts social media posts, blog outlines, changelog announcements, product launch copy, and developer content. Trigger when asked to write social posts, blog content, announcements, launch copy, or atomize strategy docs into publishable content.
Build a UI prototype for design exploration. Creates a self-contained, unauthed page in the real web app with mock data, exposes it for preview, and runs visual audits. Use when exploring layouts, information architecture, or interaction patterns before committing to production implementation.
Build a self-contained UI prototype for design exploration. Creates an unauthed page in the real web app with stress-test mock data, exposes the dev server for preview, and runs visual audits at mobile and desktop viewports. Use when exploring layouts, information architecture, or interaction patterns before production implementation.
Go code review specialist for VM Agent and CLI. Reviews PTY/WebSocket/JWT code, CLI command contracts, static-analysis findings, and Go idioms. Use when working in packages/vm-agent/, packages/cli/, or reviewing Go code changes.
| name | engineering-strategy |
| description | Engineering strategy and technical planning. Builds roadmaps (Now/Next/Later), technology radar, build-vs-buy analyses, and tech debt registers. Trigger when asked about roadmap planning, technology evaluation, build-vs-buy decisions, or tech debt prioritization. |
| user-invocable | true |
Develop and maintain engineering strategy artifacts stored in strategy/engineering/.
Before creating any artifact, read:
strategy/engineering/ for existing engineering docsstrategy/competitive/feature-matrix.md for feature gapsstrategy/business/ for business prioritiesapps/www/src/content/docs/docs/architecture/ for public architecture documentationspecs/ for feature specifications and statustasks/ for current backlogAvoids false precision of timeline-based roadmaps. Now = committed work; Next = planned, dependencies identified; Later = important but unscheduled. Each item links to a business driver.
Four quadrants (Techniques, Tools, Platforms, Languages/Frameworks) x four rings (Adopt, Trial, Assess, Hold). Include rationale and last-assessed date per entry.
Weighted scoring on: strategic differentiation, time to value, maintenance burden, integration complexity, total cost (2yr), vendor risk. Include TCO comparison and reversibility assessment.
Categorize as Reckless/Prudent x Deliberate/Inadvertent. Track priority, location, impact, remediation approach, effort estimate, and business case.
Save to strategy/engineering/:
roadmap.md — Now/Next/Later with dependencies and business driverstech-radar.md — Technology assessments by quadrant and ringtech-debt.md — Prioritized register with effort estimatesadr/NNN-[title].md — strategy-local architecture decision records; public architecture docs belong under apps/www/src/content/docs/docs/architecture/When helping prioritize, consider: business impact, competitive necessity (table-stakes?), technical leverage (unlocks future work?), user demand (evidence from support/reviews), effort, and dependencies.
Last Updated date and update trigger on every document