.claude/skills/engineering-strategy/SKILL.md
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.
npx skillsauth add raphaeltm/simple-agent-manager engineering-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 prioritiesdocs/adr/ for existing architecture decisionsspecs/ 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 — Architecture Decision Records (also consider docs/adr/ for implemented decisions)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 documentdevelopment
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
data-ai
Orchestrate multi-step workflows by decomposing into subtasks, dispatching them, and monitoring via foreground polling loops. Prevents session timeout kills during long-running orchestration. Use when coordinating multiple agents or running multi-phase work that takes more than a few minutes.
development
Marketing strategy and positioning. Builds positioning documents, messaging guides, content calendars, channel strategy, and gap analyses. Trigger when asked about positioning, messaging, marketing gaps, content planning, or channel strategy.