schematic

Generate an 11-section product and technical specification from a git branch diff.

229|23|Updated Feb 15, 2026

Search Tags:#architecture #documentation #onboarding #technical-design #branch-analysis #reverse-engineer #product-spec

Ready to run

npx skills add https://github.com/blader/schematic --skill schematic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schematic
Source: https://github.com/blader/schematic/tree/main
Command: npx skills add https://github.com/blader/schematic --skill schematic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverse engineer a detailed product and technical specification from a git branch's implementation. This enables teams to generate cohesive docs when branches ship or are in-progress, or for onboarding to unfamiliar feature branches.

Core Features & Use Cases

Automatically analyzes a branch's file changes to produce a structured specification that covers problem statement, product requirements, architecture, technical design, file inventories, testing strategy, rollout plan, and risks.
Executes parallel exploration and cross-checks to ensure completeness across large diffs.
Produces a consistent Markdown document suitable for PR descriptions, design docs, and onboarding.

Quick Start

Provide a branch diff to the skill and request a complete spec document.

Frequently Asked Questions about schematic

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

FAQPage Schema

How do I generate technical documentation from a git branch diff?▼

To generate technical documentation from a git branch diff, provide the diff to the system. It reverse engineers the implementation into a structured 11-section specification covering product requirements, architecture, and technical design.

Can I reverse engineer a product spec from an existing feature branch?▼

Yes, you can reverse engineer a product spec from an existing feature branch. The system analyzes the full file diff to produce a structured specification covering problem statements, rollout plans, and risks.

What is the best way to onboard developers to an unfamiliar feature branch?▼

The best way to onboard developers to an unfamiliar feature branch is by generating a cohesive spec document from the code changes. This captures the architecture, technical design, and file inventories in consistent Markdown.

Does this branch analysis tool handle large diffs with many changed files?▼

Yes, this branch analysis tool handles large diffs by executing parallel exploration and cross-checks. This ensures every changed file is accounted for and the output includes a complete file inventory.

How do I create a PR description from my git branch implementation?▼

To create a PR description from your git branch implementation, run the diff through the system. It produces a consistent Markdown document suitable for PR descriptions, design docs, and onboarding.

What sections are included in a reverse engineered product specification?▼

A reverse engineered product specification includes 11 sections covering the problem, product requirements, architecture, technical design, file inventories, testing strategy, rollout plan, and risks.