Skip to content

Skills as atomic building blocks — refactor skills/templates architecture #45

@codevibesmatter

Description

@codevibesmatter

Summary

Refactor the skills/template architecture so that skills become atomic, reusable methodology modules with gates, and templates become thin YAML skeletons that wire skills together.

Problem

7 of 12 current skills duplicate their template's content (phase flows, orchestration instructions, step-by-step guidance). Claude gets double context. Mode skills exist because other communities use skills AS modes — but we have kata infrastructure (templates, tasks, gates, stop hooks) so skills should provide methodology, not duplicate workflow.

Proposed Architecture

  • Templates = thin YAML skeletons (~30 lines): phases, ordering, expansion patterns, skill references
  • Skills = atomic methodology modules: instructions + gates, reusable across modes
  • mode_skill = top-level role loaded on mode entry (e.g. orchestration)
  • skill: on steps = per-step methodology injection (e.g. tdd, code-review)
  • Skills own their gate conditions (co-located with instructions)
  • Dynamic expansion (spec phases, VP steps, interviews) stamps out steps with skill references

Research

See planning/research/2026-04-06-skills-structure-deep-research.md

Key Changes

  1. Replace 7 mode skills with ~15 cross-cutting atomic skills
  2. Add gate: field to skill frontmatter
  3. Strip template step instructions to 1-2 lines + skill reference
  4. Keep existing expansion patterns (spec phases, VP steps, interview categories)

Metadata

Metadata

Assignees

No one assigned

    Labels

    approvedSpec approved — ready for implementationstatus:todoNot yet started

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions