software-architect_skill

Overview

This skill provides a systematic architecture analysis and delivery workflow using Understand → Research → Specify → Decompose → Plan. It helps turn vague requirements into measurable specifications, evaluated solution options, and an executable development plan. Use it to make build-vs-buy decisions, reduce risk, and enable parallel development for faster delivery.

How this skill works

The skill first extracts core problems, constraints, assumptions, and success criteria from your prompt or conversation. It then researches candidate solutions, rates them on maturity, fit, cost and risk, and produces spec templates. Next it decomposes the system into 1–3 day tasks, maps dependencies, and generates a phased execution plan with owners, effort, and acceptance criteria.

When to use it

• When you need a structured system design or architecture recommendation
• To evaluate build vs. buy trade-offs for a feature or platform
• When planning a project that should run in parallel streams to save time
• To decompose a large project into actionable short tasks
• When you need measurable success criteria and risk-aware plans

Best practices

• Start by clarifying the real user problem and success metrics before designing
• Research existing tools and patterns first—avoid reinventing common components
• Keep tasks small (1–3 days) and mark them as independent, sequential, or parallel-ready
• Make dependencies explicit to enable safe parallel work and reduce blockers
• Document trade-offs and assumptions so decisions can be revisited

Example use cases

• Design a scalable API and choose between managed API gateway vs custom solution
• Decide whether to build an internal search service or integrate a third-party provider
• Plan parallel implementation of infrastructure, data models, and CI/CD to shorten timelines
• Break down a monolith migration into phased components with clear dependencies
• Create acceptance criteria and risk register for a security-sensitive feature