writing-skills

To turn tacit process knowledge into testable documentation, use a test-driven approach that enforces YAML frontmatter with name and description, paired with a Markdown body for context activation. This standardizes process guides before team deployment.

Structuring a new skill requires defining YAML frontmatter containing name and description, followed by a minimal Markdown body. This format ensures the skill document loads properly into context for activation across standardized process workflows.

Yes, you can verify process documentation using a test-driven development workflow. By baselining with failing tests and applying a red-green-refactor cycle, you ensure the skill improves behavior before deployment.

The best way to standardize process-writing skills is enforcing documentation quality control through clear sections, targets, and constraints. This maintains consistent quality by turning tacit knowledge into repeatable documentation.

No specific dependencies are required to create and edit process-writing skills. The skill operates independently using a structured template of YAML frontmatter and Markdown body to codify and verify process documentation.