skill-design-lineage

Track design document revisions with YAML frontmatter and branch history.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/mhdxbilal/Ai --skill skill-design-lineage-mhdxbilal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-design-lineage
Source: https://github.com/mhdxbilal/Ai/tree/main/.claude/skills/skill-design-lineage
Command: npx skills add https://github.com/mhdxbilal/Ai --skill skill-design-lineage-mhdxbilal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist design documents from brainstorming and planning sessions with branch tracking, revision chains, and cross-session discoverability. Design docs are immutable after creation -- new revisions supersede prior versions rather than editing in place.

Core Features & Use Cases

  • Branch and revision tracking to preserve a complete history of decisions.
  • Immutable design documents with superseding revisions for auditability.
  • Cross-session discovery that surfaces relevant designs during flow-discovery and development.

Quick Start

Save a new design document to the standard designs directory with proper frontmatter.

Frequently Asked Questions about skill-design-lineage

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

FAQPage Schema
How do I track design document revisions across different branches?

Persist immutable design documents with full revision history by storing them under ~/.claude-octopus/designs/<project-slug>/ with YAML frontmatter. This preserves a complete history of decisions without editing original files in place.

What is immutable design lineage and how does it work for documentation?

Immutable design lineage preserves design documents as permanent records after creation. New revisions supersede prior versions instead of modifying originals, ensuring complete auditability of design decisions across brainstorming and planning sessions.

Can I use this for cross-session design discovery during development workflows?

Yes, cross-session discovery surfaces relevant design documents during flow-discovery and development. Designs persist under a standard project directory and remain accessible across sessions to maintain context for ongoing planning and define workflows.

Do I need YAML frontmatter to save design documents with versioning?

Yes, YAML frontmatter with branch, user, created, and supersedes fields is required to enable branch tracking and revision chains. This metadata allows the system to link revisions and maintain full design history accurately.

When should I not use in-place editing for design history and traceability?

Avoid in-place editing when you need strict auditability and traceability of design decisions. Use superseding revisions instead to preserve original documents, ensuring a verifiable chain of changes for compliance and historical review.