drafts-tiered-system

Standardize L1–L9 draft creation, promotion, consolidation, and indexing under docs/specs/drafts.

4|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/yoyooyooo/logix --skill drafts-tiered-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drafts-tiered-system
Source: https://github.com/yoyooyooo/logix/tree/main/.codex/skills/drafts-tiered-system
Command: npx skills add https://github.com/yoyooyooo/logix --skill drafts-tiered-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill prevents draft-system chaos by standardizing how teams create, organize, promote, consolidate, and index L1–L9 drafts under a single root directory.

Core Features & Use Cases

  • Tiered draft management (L1–L9): Enforces maturity-based placement where new ideas start at L9 and move toward L1 as they stabilize.
  • Topic-based consolidation: Guides collecting related L* drafts into topics/<topic-name>/ once they form a coherent theme.
  • Spec-ready writing conventions: Provides a recommended frontmatter schema (e.g., id, title, status, value, priority, depends_on, related) and a structured spec template for US/FR/NFR/SC items.
  • Operational workflow support: Defines end-to-end processes for “create new drafts,” “triage and move forward,” “consolidate,” and “integrate into formal specs” while keeping an index in sync.

Quick Start

Use this instruction to generate a new draft compliant with the tiered system: create a new L9 draft named "Agent boundary notes" under the drafts root docs/specs/drafts with status draft, value background, and priority later, including the required frontmatter and a first-pass spec structure.

Frequently Asked Questions about drafts-tiered-system

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

FAQPage Schema
How do I manage draft documents by maturity using a tiered system?

A tiered L1–L9 draft system organizes documents by maturity, starting new ideas at L9 and promoting them toward L1 as they stabilize. It enforces tier placement conventions and maintains an index for traceability.

What is the best way to consolidate related draft specifications into a topic?

Topic consolidation groups related L* drafts into a specific topics directory once they form a coherent theme. This process maintains document indexing and dependency tracking while keeping an index in sync.

How do I create a new draft with required frontmatter and spec template?

Create a new draft under the root directory using a structured spec template for US/FR/NFR/SC items. Apply the recommended YAML frontmatter schema including id, title, status, value, priority, depends_on, and related fields.

How does dependency tracking work for draft documents in a tiered pipeline?

Dependency tracking uses YAML frontmatter fields like depends_on and related to establish stable cross-references. This relationship semantics ensures traceability when promoting or consolidating drafts across the L1–L9 maturity levels.

Can I use YAML frontmatter for document discovery in a draft management system?

Yes, the draft system satisfies YAML-frontmatter-based discovery needs by using name and description as entry points. This frontmatter schema enables reliable document indexing and knowledge organization across drafts.

When should I integrate mature drafts into formal specifications?

You should integrate drafts into formal specifications when they reach lower L-tiers and achieve stability. The operational workflow defines end-to-end processes for triage and integration while keeping the draft index in sync.