solution-designer

Produces requirements docs, investigation notes, and design specs for software engineering tasks.

2|1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/AutoByteus/autobyteus-agents --skill solution-designer-autobyteus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solution-designer
Source: https://github.com/AutoByteus/autobyteus-agents/tree/main/agent-teams/software-engineering-team/agents/solution-designer/skills/solution-designer
Command: npx skills add https://github.com/AutoByteus/autobyteus-agents --skill solution-designer-autobyteus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a raw engineering request into an approved, implementation-ready design is error-prone: requirements stay vague, current-state behavior goes uninvestigated, and design decisions lack evidence. This Skill structures that entire upstream workflow so designs are grounded in verified evidence and pass architecture review. ## Core Features & Use Cases - Mandatory Core Artifacts: Generates a requirements doc, investigation notes, and a design spec from structured templates, plus a solution revision record tracking every review round. - Evidence-Backed Investigation: Records exact sources, commands, runtime probes, and stable behavior IDs so downstream reviewers never rediscover facts. - Design Health & Migration Decisions: Classifies root causes, decides refactor posture, and makes explicit persisted-data transition decisions (no migration, rebuild, or migration plan). - Use Case: A team receives a feature request touching an existing codebase. The Skill bootstraps a dedicated git worktree, investigates current behavior, refines requirements with the user until approved, produces a spine-and-ownership design spec, and iterates with the architecture reviewer until the design passes. ## Quick Start Ask the agent to investigate this task and produce the requirements doc, investigation notes, and design spec for architecture review.

Frequently Asked Questions about solution-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature request into an implementation-ready design spec?▼

This Skill bootstraps a task workspace, investigates current behavior with recorded evidence, refines a requirements doc until approved, then produces a design spec using spine, ownership, and file-responsibility mapping. The package iterates with an architecture reviewer until it passes.

What artifacts does a solution design workflow produce?▼

It always produces three core artifacts: a requirements doc, investigation notes, and a design spec, plus a solution revision record. Optional supplements like UI/UX specs or API contracts are added when they materially improve clarity.

Does the design workflow require a dedicated git worktree?▼

Yes, for git-repository tasks it requires a dedicated ticket worktree/branch created from the latest tracked remote base. If worktree creation fails, the task stays in Draft status and the blocker is recorded.

When is a data migration required in a design spec?▼

Migration is required only when evidence shows existing persisted data cannot be directly used or rebuilt. The design must then define an explicit migration boundary, keeping historical-schema handling out of current business code.

What happens when the architecture reviewer finds a requirement gap?▼

The requirements doc, investigation notes, and affected supplements are revised, a new SR-* entry is appended to the revision record, and the full package is resent. Scope-changing proposals need explicit user approval first.