apptension/apptension-sdlc
Apptension SDLC processes as skills, each carrying its own portable agent contract for how we work.
Use when opening the Cezar cockpit for the repo it is configured in — finding an already-running cockpit and returning this project's URL rather than starting a second one. Trigger on intent like "open Cezar", "start the cockpit", "show me the dispatched tasks", "where is that run".
Use when configuring Cezar as a repo's task orchestrator — deriving its base branch from the repo's bindings, writing .ai/cezar/config.json, and verifying a run can reach the SDLC skills. Trigger on intent like "set up Cezar here", "configure the orchestrator", or when the setup skill offers it. Safe to re-run at any time; re-run it whenever the branching model changes.
Use when judging whether a pull request's docs kept up with its change, in CI or on request, drafts included, or when setting up that check in a repo. Trigger on intent like "check this PR's docs", "did the docs keep up", "run the docs drift check on PR
Plugin availability for the SDLC skills, called by run-preflight, setup, cezar-setup and pr-checks. Checks whether superpowers is in the session, picks full or reduced mode, announces reduced mode, and gives this harness's install path.
Use when installing automated code review in a repo — copying the bundled review workflow, scripts, prompt, and schema, substituting only the per-repo keys. Trigger on intent like "set up automated code review", "install the review workflow", "set up automated PR review for this repo", or when the setup skill offers it for the automated-review-workflow gap. Safe to re-run; a repo whose files already match is a no-op.
Use when creating a project-owned skill to launch and drive the real application, or when setup identifies a missing project verification skill.
Use when working a ticket in this repo — a GitHub issue or a Jira ticket, per the Issue tracker binding — taking it to a draft PR. Covers pre-flight checks, branch naming, the design gate (when brainstorming can be skipped), project-board or Jira status sync, verification, and the required draft-PR body. Trigger on intent like "work issue
Manual skill, run when the human names it or dev-flow invokes it. Working a ticket end to end is dev-flow. Takes a ticket's plan to a draft PR, and run on its own asks at most one question, the execution method, then nothing until the PR is open.
Use when a repo has no .github/ISSUE_TEMPLATE/task.yml. Writes one from a bundled template, filling the Area dropdown from the repo's own labels instead of another repo's taxonomy. Trigger on intent like "add a task template", "this repo has no task.yml", when issue-authoring finds no template to file against, or when the setup skill offers it for the issue-template gap. Safe to re-run, and an existing task.yml is left as it is.
Use when drafting a new issue for the target repo's tracker — filing it directly via gh issue create under GitHub, against .github/ISSUE_TEMPLATE/task.yml with the area conveyed as a label instead of the form's dropdown, or via jira_create_issue under Jira — with acceptance criteria that describe shipped work rather than a design-only outcome. Trigger on intent like "file an issue for X", "draft a GitHub issue", "let's write up this issue", or "open a task for this".
Use when a new issue is opened in this repo, to check it for duplicates and apply best-fit labels from the repo's label set. Trigger on intent like "triage issue
Use when auditing a project's verification instructions and feature map, or when a scheduled verification maintenance run supplies a target skill and report path.
GitHub issue handling, called by plan-issue, implement-issue, dev-flow and issue-authoring. Reads, comments on, moves and assigns a GitHub issue, and returns the reference its pull request carries.
Jira ticket handling, called by plan-issue, implement-issue, dev-flow, setup and issue-authoring. Reads, comments on, transitions and assigns a Jira ticket, checks every write against the recorded site, returns the reference its pull request carries, and finds or configures the Jira server entry.
Manual skill, run when the human names it or dev-flow invokes it. Working a ticket end to end is dev-flow. Plans a ticket through the design gate, and run on its own posts the plan to the ticket for a later implement-issue run.
Use right after opening a draft PR in this repo (the tail of the draft-PR step in dev-flow or implement-issue) to start watching CI and review feedback and auto-fix what it can. Trigger on intent like "draft PR is open, keep watching", "monitor this PR", or "watch CI and review comments".
Worktree pruning, called by implement-issue and pr-checks. Removes worktrees whose pull requests merged, sweeping from the current checkout or from the main checkout.
Pre-flight for a ticket, called by plan-issue, implement-issue and dev-flow. Resolves the ticket's tracker, reads the ticket, runs the readiness checks and picks full or reduced mode.
Use when the user explicitly asks to set up or adopt the Apptension SDLC in a repo — auditing the repo against the process checklist, recording its bindings in CLAUDE.md, and filing an issue per remaining gap. Trigger on intent like "set up the SDLC here", "adopt apptension-sdlc in this repo", "audit this repo against our process", "run setup", or "re-run setup after the plugin update". Do not invoke on your own because a bindings section is missing — suggest it instead.
Use when installing or updating scheduled maintenance for a project-owned verification skill, including when setup offers maintenance after finding or creating that skill.