Cheatsheet 📋¶
Each operator workflow has a skill that routes the agent to its authoritative
procedure and drives it — clarifying open requirements first, then acting
autonomously to completion. Most are i8- skills specific to this repository; a
few (such as triage) are portable skills shared across projects.
How to use 🧭¶
Invoke a skill with its slash command, for example /i8-develop or /i8-quality,
or name the skill in your message to the agent. Supply the concrete target (role,
scope, requirement file, or run URL) in the same message; the skill fills the rest
from its procedure file. Run make install-skills to (re)install them.
Skills 🗂️¶
Situation |
Skill |
|---|---|
Building a new feature, app, or larger change |
|
Iterating a web app role in compose mode |
|
Iterating a web app role in swarm mode |
|
Validating every role across both modes, compose then swarm |
|
Iterating on |
|
Iterating on a GitHub Actions workflow |
|
Writing or updating a Playwright spec for a |
|
Running or validating tests for a specific scope |
|
Running the quality gate ( |
|
Running the full gate ( |
|
Cleaning up code, docs, or roles after a change |
|
Checking a branch out into a parallel worktree |
|
Releasing a parallel worktree and its slot |
|
Freeing disk space and |
|
A GitHub Actions / CI run failed and needs triage |
|
A local deploy is failing on the host |
|
Inspecting a |
|
Pulling a sibling feature branch and merging it into the current one |
|
Staged changes are ready to be committed |
|
A branch is ready to be opened as a pull request |
|
Pushing a branch through the manual-CI draft → ready-for-review cycle |
|
Writing the blog article, banner image and social posts for a release |
|
Writing a new requirement |
|
Implementing an existing requirement file end to end |
|