skill-phase-formatter

Split domain Skills into phase-aware files and sync design.md and constraints.md.

15|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kousukef/forge --skill skill-phase-formatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-phase-formatter
Source: https://github.com/kousukef/forge/tree/main/skills/skill-phase-formatter
Command: npx skills add https://github.com/kousukef/forge --skill skill-phase-formatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase-aware file structuring helps maintain a single source of truth by dividing a domain Skill into SKILL.md, design.md, and constraints.md, and defines the rules for synchronization and validation.

Core Features & Use Cases

  • SSOT-driven workflow: SKILL.md remains the master source, with derived files reflecting its content
  • Synchronization and validation: changes propagate and are checked against structure rules
  • Practical use: when restructuring a large domain Skill, align design/constraints with the SKILL.md entry

Quick Start

Run the phase formatter on a domain Skill to generate phase-aware files and synchronize design.md and constraints.md back to SKILL.md.

Frequently Asked Questions about skill-phase-formatter

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

FAQPage Schema
How do I split a large domain SKILL.md into separate design and constraints files?

Split domain SKILL.md files into phase-aware structures by generating separate design.md and constraints.md files. This standardizes documentation and enforces a single source of truth for your workflow.

What is phase-aware structuring for domain skills?

Phase-aware structuring divides a domain skill into SKILL.md, design.md, and constraints.md files. It defines synchronization and validation rules to maintain documentation consistency across all phases.

How do I synchronize design.md and constraints.md updates back to SKILL.md?

Synchronize design.md and constraints.md updates back to SKILL.md by running the phase formatter. Changes propagate and are checked against structure rules to maintain consistency.

When do I need to restructure a domain skill into phase-aware file structures?

Restructure domain skills into phase-aware file structures during maintenance of large skills. This aligns design and constraints documentation with the SKILL.md entry to standardize workflows.

What are the line-count constraints for design.md and constraints.md files?

Line-count constraints are enforced for design.md and constraints.md files during synchronization. The formatter validates these files against structure rules and subset relationships to maintain documentation quality.

Can I maintain a single source of truth across multiple skill documentation files?

Maintain a single source of truth by keeping SKILL.md as the master source. Derived design.md and constraints.md files reflect its content automatically through synchronization and validation rules.