writing-skills

Process documentation codifies tacit knowledge into reusable skill formats by capturing repeatable workflows, standardizing them with clear structure (core principle, steps, examples, edge cases), and sharing them across teams. This ensures consistent practices and enables knowledge transfer without repeated explanation.

Use test-driven documentation: first document baseline failures (RED), then write the skill to address them (GREEN), then test and refine it (REFACTOR). This cycle ensures your documentation solves real problems and prevents repeated mistakes.

Structure skills using four types (Discipline, Technique, Pattern, Reference) with a comprehensive document format including core principle, process steps, concrete examples, and edge cases. This standardized structure ensures clarity, completeness, and cross-model applicability.

Yes. When you notice repeated errors in your workflow, document those failures as baseline test cases, then create a skill with clear rules and examples to prevent them, and refine it through testing. This converts tacit warnings into actionable documented patterns.

A reusable skill addresses a repeatable workflow or common problem your team encounters multiple times. It should have discoverable patterns, clear steps, and applicability across contexts—such as testing anti-patterns, onboarding procedures, or community contribution workflows.

No. Start with observed problems in your workflow. Identify where developers struggle, document those baseline failures, then build the skill around solving them. The test-first approach works with minimal prerequisites and builds documentation iteratively.