kata-engineering

Implement features, fix bugs, start new projects, or bootstrap project structure. Use for any coding task — writing or modifying code on any project, even small edits.

Initialize this computer with the Kata Engineering framework for Codex and/or Claude.

Review code changes, check project health, verify contract compliance, or refresh living docs (PLAN.md, DECISIONS.md). Use for any review or project health task.

Sweep the project's filenames and folder layout for product-readability. Form independent assumptions first, then propose or apply renames that survive a fresh-eyes test.

Bootstrap a project knowledge base — folder skeleton, entity-page design, SCHEMA/CLAUDE/README scaffolding, an ingest-sources skill, .gitignore, git init, and initial commit. Use when the user wants to set up a knowledge base or queryable source of truth for a stakeholder-heavy project with meetings, emails, and documents.

Process new emails, meeting transcripts, Word documents, presentations, and PDFs dropped into sources/ and distill them into entity pages (people, organizations, workstreams, commitments, decisions, change-requests, risks, assumptions, dependencies, stakeholders, milestones, integrations, budget, meetings). Also updates SOURCES-CHECKLIST.md. Use when the user says "ingest sources", "process new sources", "update the knowledge base", or drops new files into any sources/ subfolder and asks to process them.

Turn a rough project idea into a structured starting point before execution begins. Use this skill whenever starting something new from a vague idea — it interrogates the concept, challenges weak assumptions, and produces a Project Brief, Research Brief, phased project shape, execution plan, and a refined kickoff prompt ready to hand to an agent.