Skip to content

KunanonJ/superstacks / plugins/superstacks/skills/ticket-pipeline

ticket-pipeline

Verified

Use when running a ticket from discovery through a draft PR. Sequences how, plans, verify-loop, TDD, verification, review, optional interrogate, then pr.

Ticket pipeline

Run a ticket from discovery through a draft pull request. safety-overrides beat every step.

Put evidence in the PR body under the headings this skill names. Then run the status script. Do not argue in prose about which steps are done:

python <this-skill>/scripts/pipeline_status.py --pr-body BODY.md

Re-run until the script prints missing: 0.

Sequence

  1. ama — make the assignment clear: look first, ask the owner only what is unclear. No heading needed.
  2. how — build a mental model before changing code. Heading: ## How.
  3. writing-plans — plan in the pull request body. Heading: ## Plan.
  4. verify-loop — define the deterministic check, run it red (VERIFY_FAIL), then iterate.
  5. test-driven-development — if the check is a test: failing test, then minimal code. Heading: ## TDD (include red-green).
  6. verification-before-completion — paste fresh verify-loop runner output. Heading: ## Evidence.
  7. code-review — Standards and Spec axes on the branch diff. Heading: ## Code review.
  8. interrogate — required for one-way doors (money movement, schema or data migrations, auth, data deletion, infra or prod config, licences). Heading: ## Interrogate, or write N/A (two-way door).
  9. pr — draft pull request body. Run pr/scripts/check_pr_body.py. Ticket links are Refs #N only.

Hard rules (also in safety-overrides)

  • Draft PRs. Never mark ready. Merge only as trust_level in safety-overrides allows. Read the owner's recorded decisions through owner-decisions first; with none, a human merges.
  • Push only this branch. Rewrite with --force-with-lease only.
  • No production credentials, live infrastructure, runtime package installs, or secret-using CI jobs.
  • No tracker or chat writes from a ticket.
  • Skip a blocking approval gate only with Ruling: what / why in the PR body.

Stacked pull requests

When one ticket is too large for a single reviewable PR, split it into layers:

  • One concern per layer. Dependencies belong in the same layer or a lower one.
  • Open the next layer while the lower one is still in review.
  • Merge bottom-up. When merging through the API, use the asynchronous merge endpoint for stacks.
  • Prefer gh stack for cascading rebases. If stacks are unavailable, chain pull requests with plain base-branch targeting.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall