with one click
creating-process-files
// Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files.
// Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files.
Presents a proposed approach in progressive confirmable chunks with recommended decisions and alternatives. Use when aligning on a design, plan, or technical approach before implementation.
Iterative code refactoring through progressive lenses via a worker-reviewer agent team.
Launches agent teams with structured roles and task decomposition. Use when asked to create a team, spawn teammates, or coordinate multiple agents in parallel.
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent design, acceptance test, component test, walking skeleton, in-memory fakes, component, contract test, adapter, fast tests, sub-second feedback. Language-agnostic (Go, Rust, Python, TypeScript, Java, C#).
Writes Claude Code status line scripts. Use when creating, customizing, or debugging statusline configurations.
Designs systems using Event Modeling.
| name | creating-process-files |
| description | Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files. |
STARTER_CHARACTER = ⚙️
This skill helps make new process files or fine tune existing ones. A process file describes a structured sequence of steps for AI to follow to create a predictable output. Process files are content neutral to the project.
This process has these distinct phases:
Ask one question at a time. If you are giving options, give a list to choose from.
Create the initial version of the process file, or revise it if it already exists. Ask to review it.
Read the draft created in phase 2. Check for inconsistencies, contradictions, or missing information. If any are found, ask clarifying questions one at a time.
Review the process file created in phase 2 and simplify. Be as concise as possible.
For an example of a process file, examine this file itself.