skill design lineage

Design Community

Skill notes

Storage Location

All design documents are stored under: The project slug is derived from the current git repository name or working directory basename:

Filename Format

Design documents follow a strict naming convention: Where: {user} -- the current OS username ($USER or whoami) {branch} -- the current git branch, sanitized (slashes replaced with dashes) {datetime} -- ISO 8601 compact timestamp (YYYYMMDD-HHmmss)

Design Document Template

Each design document contains YAML frontmatter followed by structured sections.

Frontmatter Metadata

Fields: branch -- the git branch at time of creation user -- the OS username who created the document created -- ISO 8601 timestamp of creation supersedes -- filename of the prior design document this revision replaces (omitted if this is the first design for the branch)

Step 1: Save Design

After a brainstorm, planning, or define workflow produces design output, save it to the standard location with metadata. Design docs are read-only after creation. To revise a design, create a new document with a supersedes reference to the prior version.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Save Design

After a brainstorm, planning, or define workflow produces design output, save it to the standard location with metadata. Design docs are read-only after creation. To revise a design, create a new document with a `supersedes` reference to the prior version.

02
Step 2: Discover Prior Designs

Before writing a new design, search for related prior designs using keyword matching. Constraints: Keyword search is limited to 10 results to avoid overwhelming context Search is case-insensitive via `grep -li` Only searches within the current project slug's directory

03
Step 3: Link Revision Chain

If a prior design exists for the same branch, the new design document includes a `supersedes` field in its frontmatter pointing to the prior filename. This creates a linked chain of revisions: To walk the full revision history for a branch:

04
Step 4: Cross-Session Discovery

Downstream commands (deliver, review, develop) auto-discover design context by checking the designs directory before starting work. Downstream skills should check for designs before starting work: flow-discover: Check for existing designs to avoid duplicate research flow-define: Incorporate prior design constraints into requirements flow-develop: Read the recommended approach from the latest design

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.