AGENT SKILL

checks-recipe

The method for the checks stage of a full-lane change: read the plan, run the project checks once, and report each failure. Use when you are the paqad checks stage agent.

License 许可
MIT
所属仓库
Eliyce/paqad-ai
最近更新
2026-11-13
Stars
★ 8
Forks
0

01 前言 Front Matter

name
checks-recipe
metadata
{ "cacheable": "false", "model_tier": "reasoning", "paqad-meta": "skill.meta.yaml", "output_format": "markdown" }
description
The method for the checks stage of a full-lane change: read the plan, run the project checks once, and report each failure. Use when you are the paqad checks stage agent.

02 资源文件 2

03 SKILL.md 正文

What It Does

Gives the checks stage its short method. checks plan and checks run are the method.

Use This When

You are the paqad stage agent for this stage. Your injected copy is the truth for this stage; the source skills it copies stay for their other workflows.

Inputs

  • The request and review.json from paqad-ai stage begin checks, which also prints the checks plan.

Procedure

  1. Restate the request and its acceptance criteria in two lines at the top of your return.
  2. Work quickly: skip anything this stage doesn't need, and return as soon as the result is correct.
  3. Run the project command checks after implementation and before finalizing the feature.
  4. Read the plan paqad-ai stage begin checks printed.
  5. Run paqad-ai checks run once. Do not repeat a green run, and do not edit anything to make a check pass.
  6. End with paqad-ai stage end checks --agent paqad-checks --artifact <the checks.json path>.
  7. Return Status: DONE only when every check is green. Otherwise return Status: DONE_WITH_CONCERNS, one line per failing check.

Read This Path

  • When the plan prints test: sequential (unknown), read base/skills/test-runner-discovery/SKILL.md under the install directory that .paqad/framework-path.txt names.

Output Contract

  • checks.json from paqad-ai checks run, and one line per failing check.

Escalate / Stop Conditions

  • A check with no mapped command: return Status: NEEDS_CONTEXT naming it.

04 同仓库更多 Skills

Eliyce
Eliyce/paqad-ai

sample-skill

Sample bundled skill fixture

★ 8
Eliyce
Eliyce/paqad-ai

processing-invoices

Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.

★ 8
Eliyce
Eliyce/paqad-ai

processing-invoices

Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.

★ 8
Eliyce
Eliyce/paqad-ai

understand-idea

Chat and Claude Code: Step 1 of the discover journey: clarifies the goal, who benefits, success and constraints into the idea block. Use when the journey directs it to step 1, not directly.

★ 8
Eliyce
Eliyce/paqad-ai

size-work

Chat and Claude Code: Suggest a size for a ticket from comparable finished work, as a labelled suggestion the team still owns. Use it when someone asks "how big is this?", "roughly how much work is ABC-12?", or wants a backlog item sized. It finds the team's sizing scale at first use, picks two to five of the closest finished tickets with links, and gives a size or range with the drivers behind it and a confidence of low, medium or high, lowered and explained when the area's documents are template text. Every result is labelled a suggested size, never a date or a commitment. It writes nothing into the size field unless the user says "set it", and it refuses to overwrite an existing size unless the user asks to replace it. Produces the sizing block of the record.

★ 8
Eliyce
Eliyce/paqad-ai

refine-ticket

Chat and Claude Code: Improve one or more existing tracker tickets without losing the author's intent. Use it when someone wants a ticket read, diagnosed and tidied up ("this ticket is vague", "fix up ABC-12", "split this, it's too big"). It reads each ticket in full and snapshots it with its last-updated time, says what is wrong with evidence, and proposes a field-by-field before and after change set limited to summary, description, labels, parent, links and new child tickets on a split. It writes nothing until an explicit "apply it" bound to that exact change set, re-checks the ticket for conflicting edits just before writing, never replaces rich descriptions with plain text, never deletes or closes a ticket, and reads each ticket back after applying. Produces the existing and changes blocks of the record.

★ 8