nullvoidundefined
@nullvoidundefined
Public Skills
task-start
by nullvoidundefined
Use at the beginning of any work, before deciding whether it needs a spec, a plan, TDD, a branch, a worktree, or subagents.
task-start
by nullvoidundefined
Use at the beginning of any work, before deciding whether it needs a spec, a plan, TDD, a branch, a worktree, or subagents.
task-start
by nullvoidundefined
Use at the beginning of any work, before deciding whether it needs a spec, a plan, TDD, a branch, a worktree, or subagents.
session-start
by nullvoidundefined
Use at the start of every interactive Codex session, before any other work, to run the R-001 session-start procedure: memory index, handoff, session type, Tier 2 files, project instructions. A non-interactive codex exec invocation skips it.
task-cleanup
by nullvoidundefined
Use at the end of every task, before calling the work done or merging a feature branch. Pairs with task-start.
build-by-slice-require-review
by nullvoidundefined
Use when running a feature build as slices of PRs, starting a slice, or executing any multi-PR build. The owner approves the slice plan once at Gate 1 and chooses that slice's merge mode there: by default they read and merge each PR, or they opt in to the session merging on green CI and running on. Triggers on "start the slice", "next slice", "build this slice by slice", or "implement with review gates". For the in-harness TDD slice mechanics under the R-412 lock, tdd-gated-dispatch owns the trigger.
build-by-slice-require-review
by nullvoidundefined
Use when running a feature build as slices of PRs, starting a slice, or executing any multi-PR build. The owner approves the slice plan once at Gate 1 and chooses that slice's merge mode there: by default they read and merge each PR, or they opt in to the session merging on green CI and running on. Triggers on "start the slice", "next slice", "build this slice by slice", or "implement with review gates". For the in-harness TDD slice mechanics under the R-412 lock, tdd-gated-dispatch owns the trigger.
task-cleanup
by nullvoidundefined
Use at the end of every task, before calling the work done or merging a feature branch. Pairs with task-start.
task-cleanup
by nullvoidundefined
Use at the end of every task, before calling the work done or merging a feature branch. Pairs with task-start.
ticket-lifecycle
by nullvoidundefined
Use to open, advance, close, or report on the external tracker ticket (Jira, Notion, or Asana) that tracks a task. Triggers at task classification, at every state change in the work, at task close, and on "what did I ship this week" or "how long does this tier take".
ticket-lifecycle
by nullvoidundefined
Use to open, advance, close, or report on the external tracker ticket (Jira, Notion, or Asana) that tracks a task. Triggers at task classification, at every state change in the work, at task close, and on "what did I ship this week" or "how long does this tier take".
ticket-lifecycle
by nullvoidundefined
Use to open, advance, close, or report on the external tracker ticket (Jira, Notion, or Asana) that tracks a task. Triggers at task classification, at every state change in the work, at task close, and on "what did I ship this week" or "how long does this tier take".
repo-setup
by nullvoidundefined
Use when creating a new GitHub repository, or when bringing an existing one up to the hygiene baseline before its first pull request - CI workflow, Dependabot, Greptile review, protected main and staging branches, squash-only merges, security alerts. Triggers on "set up the repo", "new repo", "repo hygiene", "protect main", or "add CI".
repo-setup
by nullvoidundefined
Use when creating a new GitHub repository, or when bringing an existing one up to the hygiene baseline before its first pull request - CI workflow, Dependabot, Greptile review, protected main and staging branches, squash-only merges, security alerts. Triggers on "set up the repo", "new repo", "repo hygiene", "protect main", or "add CI".
feature-create
by nullvoidundefined
Use when starting implementation of a feature that already has an approved plan, before any code is written. Triggers on "start feature", "create feature", "kick off", or immediately after a plan is finished.
feature-create
by nullvoidundefined
Use when starting implementation of a feature that already has an approved plan, before any code is written. Triggers on "start feature", "create feature", "kick off", or immediately after a plan is finished.
tdd-gated-dispatch
by nullvoidundefined
Use for any Standard, Complex, or Saga task once a spec exists, to run each behavior as one RED/GREEN/REFACTOR/REVIEW slice with the harness proving each step. In Standard the session writes each slice's failing test itself, under the lock, then implements it; in Complex and Saga the test-author subagent writes it and the implementer and slice-critic agents run as separate fresh contexts. Codex writes the test only when the owner opts in for that slice (R-907, owner decision 2026-09-23, IAN-333). Sits between writing-plans and subagent-driven-development; the Superpowers skills stay the skeleton, this skill is the enforcement.
tdd-gated-dispatch
by nullvoidundefined
Use for any Standard, Complex, or Saga task once a spec exists, to run each behavior as one RED/GREEN/REFACTOR/REVIEW slice with the harness proving each step. In Standard the session writes each slice's failing test itself, under the lock, then implements it; in Complex and Saga the test-author subagent writes it and the implementer and slice-critic agents run as separate fresh contexts. Codex writes the test only when the owner opts in for that slice (R-907, owner decision 2026-09-23, IAN-333). Sits between writing-plans and subagent-driven-development; the Superpowers skills stay the skeleton, this skill is the enforcement.
tdd-gated-dispatch
by nullvoidundefined
Use for any Standard, Complex, or Saga task once a spec exists, to run each behavior as one RED/GREEN/REFACTOR/REVIEW slice with the harness proving each step. In Standard the session writes each slice's failing test itself, under the lock, then implements it; in Complex and Saga the test-author subagent writes it and the implementer and slice-critic agents run as separate fresh contexts. Codex writes the test only when the owner opts in for that slice (R-907, owner decision 2026-09-23, IAN-333). Sits between writing-plans and subagent-driven-development; the Superpowers skills stay the skeleton, this skill is the enforcement.
build-by-slice-require-review
by nullvoidundefined
Use when running a feature build as slices of PRs, starting a slice, or executing any multi-PR build. The owner approves the slice plan once, then the build runs without stopping. Triggers on "start the slice", "next slice", "build this slice by slice", or "implement with review gates". For the in-harness TDD slice mechanics under the R-412 lock, tdd-gated-dispatch owns the trigger.
repo-setup
by nullvoidundefined
Use when creating a new GitHub repository, or when bringing an existing one up to the hygiene baseline before its first pull request - CI workflow, Dependabot, Greptile review, protected main and staging branches, squash-only merges, security alerts. Triggers on "set up the repo", "new repo", "repo hygiene", "protect main", or "add CI".
feature-create
by nullvoidundefined
Use when starting implementation of a feature that already has an approved plan, before any code is written. Triggers on "start feature", "create feature", "kick off", or immediately after a plan is finished.
structure-conventions
by nullvoidundefined
The stack-specific structural and syntax rules (R-304, R-305, R-309 to R-314, R-319, R-321, R-323, R-324, R-326 to R-329, R-407). Use before creating, moving, splitting, or renaming a directory, module, migration, or test tree in a server or web client (TypeScript, Python, Vue, or Nuxt), before writing a pg migration or Alembic default, and when planning a package layout. Each rule here is also enforced mechanically at the tool call, so this skill is the pre-emptive read, not the backstop.
structure-conventions
by nullvoidundefined
The stack-specific structural and syntax rules (R-304, R-305, R-309 to R-314, R-319, R-321, R-323, R-324, R-326 to R-329, R-407). Use before creating, moving, splitting, or renaming a directory, module, migration, or test tree in a server or web client (TypeScript, Python, Vue, or Nuxt), before writing a pg migration or Alembic default, and when planning a package layout. Each rule here is also enforced mechanically at the tool call, so this skill is the pre-emptive read, not the backstop.