spec-design-guide

Align SPEC.md and DESIGN.md with the current codebase.

1|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/chronista-club/fleetflow --skill spec-design-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-design-guide
Source: https://github.com/chronista-club/fleetflow/tree/main/.claude/skills/spec-design-guide
Command: npx skills add https://github.com/chronista-club/fleetflow --skill spec-design-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams record and maintain living specifications and design docs that stay in sync with the codebase, reducing drift and improving maintainability.

Core Features & Use Cases

  • Living Documentation: keeps SPEC.md and DESIGN.md aligned with current code changes.
  • Workflow Integration: streamlines alignment during feature development, PR reviews, and refactors.
  • Auditable Traceability: preserves change rationale and history for governance.

Quick Start

Ask Claude to review SPEC.md and DESIGN.md and align them with the current codebase to maintain living documentation.

Frequently Asked Questions about spec-design-guide

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

FAQPage Schema
How do I keep design docs and specs in sync with my codebase?

To keep design docs in sync, align SPEC.md and DESIGN.md files with current code changes during feature development and refactoring to preserve architectural rationale and maintain living documentation.

What is living documentation and how does it reduce spec drift?

Living documentation continuously aligns SPEC.md and DESIGN.md with the evolving codebase to reduce drift, preserving change rationale and architectural intent for auditable traceability during routine development workflows.

How do I maintain design rationale traceability during refactoring?

Maintain design rationale traceability by updating SPEC.md and DESIGN.md frontmatter and accompanying change histories during refactoring, ensuring cross-references accurately reflect the current codebase state.

Do I need SPEC.md and DESIGN.md frontmatter to use living documentation sync?

Yes, accurate SPEC.md and DESIGN.md frontmatter and accompanying change histories are required to ensure cross-references and traceability function correctly when aligning documentation with the codebase.

Can I integrate spec alignment into code reviews and PR workflows?

Yes, you can integrate spec alignment into code reviews by checking SPEC.md and DESIGN.md against current changes, streamlining workflow alignment while preserving governance history.

What's the best way to prevent spec drift when updating code?

The best way to prevent spec drift is reviewing SPEC.md and DESIGN.md alongside codebase changes, applying alignment during feature development and refactoring to ensure documentation stays living.