sdd-highway

Implement code directly from target specs and record a highway-summary.md.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-highway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-highway
Source: https://github.com/eburairu/Squat-Tracker/tree/main/.agent/skills/sdd-highway
Command: npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-highway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rapid implementation by skipping formal design documents and proceeding directly to code while recording progress.

Core Features & Use Cases

  • Rapid deployment: Eliminate lengthy design cycles and move to implementation with immediate recording of decisions.
  • Traceable records: Automatically generate and store a highway-summary.md capturing outcomes and decisions for future reference.
  • Use Case: In a project with existing steering documents and target specs, use this Skill to go from requirements to a working artifact and a summarized record without intermediate design artifacts.

Quick Start

Start the highway mode using the sdd-highway skill, ensure .sdd/steering/ documents exist (product.md, tech.md, structure.md), verify .sdd/target-spec.txt is present, and confirm .sdd/specs/[spec名]/requirements.md exists. Then execute the implementation steps and save the summary to .sdd/specs/[spec名]/highway-summary.md.

Frequently Asked Questions about sdd-highway

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

FAQPage Schema
How do I skip design documents and go straight to code for rapid implementation?

To skip formal design documents for rapid implementation, use a requirements-driven approach that moves directly to code while automatically generating a highway-summary.md to record progress and decisions.

What prerequisites are needed to start fast-track development from a target spec?

Fast-track development from a target spec requires a steering directory containing product.md, tech.md, structure.md, a target-spec.txt file, and a per-spec requirements.md file before implementation begins.

How do I keep traceable records when eliminating lengthy design cycles?

To keep traceable records while eliminating lengthy design cycles, automatically generate and store a highway-summary.md file capturing outcomes and implementation decisions during direct coding.

When should I use a requirements-driven highway mode instead of formal design?

Use requirements-driven highway mode when a project already has existing steering documents and target specs, allowing you to go from requirements to a working artifact without intermediate design artifacts.

What is the best way to generate implementation summaries for fast-track development?

The best way to generate implementation summaries for fast-track development is to proceed directly to code from requirements and save a final highway-summary.md capturing the implementation outcomes and decisions.