solution-generator

Generate a team-ready specification package with master index and per-concern files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MaxDehaut/default-repository --skill solution-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-generator
Source: https://github.com/MaxDehaut/default-repository/tree/main/.claude/skills/analysis-solution
Command: npx skills add https://github.com/MaxDehaut/default-repository --skill solution-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a validated Concept Generator document into a complete, team-ready specification package that can be handed off to architects, developers, and testers.

Core Features & Use Cases

  • Produces a master index file plus one file per specification concern (functional specs, technical specs, architecture, data model, repository structure, API endpoints, technology selection, and a validation guide)
  • Organizes all files under a standard solution/ folder structure for consistent handoffs and toolchain compatibility
  • Supports traceability and alignment with Concept Generator inputs to ensure reusability across teams

Quick Start

Paste a validated Concept Generator document to generate a complete, team-ready specification package in a structured solution/ folder.

Frequently Asked Questions about solution-generator

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

FAQPage Schema
How do I turn a validated software concept into a complete specification package for team handoff?

Specification generation produces a master index and per-concern files covering functional specs, technical specs, architecture, data models, repository structure, API endpoints, technology selection, and a validation guide under a structured solution/ directory.

What is included in a team-ready solution specification for developers and testers?

A team-ready solution specification includes a master index and separate files for functional specs, technical specs, architecture, data model, repository structure, API endpoints, technology selection, and a validation guide under a solution/ folder.

Can I generate architecture and API endpoint specifications from a concept document for Claude Code?

Yes, generating architecture and API endpoint specifications from a validated concept document outputs a structured solution/ folder designed specifically to enable Claude Code handoff for development teams.

How do I structure a solution folder for software architecture documentation and technical specs?

Structuring a solution folder involves outputting a master index file and per-concern specification files for architecture, technical specs, data models, and API endpoints to ensure consistent handoffs and toolchain compatibility.

Do I need a validated concept document to generate functional specs and data models?

Yes, a validated concept document is required. Specification generation applies to concept-to-spec workflows, transforming the input into functional specs, data models, and technical architecture files for team handoff.