agentsclimarketplace

Aa resume

Skill Peeyushmeher/agent-agile/skills/aa-resume

Agile planning + execution for AI coding agents: grill the idea, plan with OKRs, adversarial critic panel with kill authority, cheap-model story cards, parallel wave execution. MIT, no token, ever.

Install
npx -y skills add Peeyushmeher/agent-agile --skill aa-resume

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user says resume, continue, or pick up where we left off, starts a new session on an existing Agent-Agile project, or is recovering after a crash or context reset, for example "/aa-resume", "let's continue", "where were we".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

aa-resume

Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.

Read playbooks/execution.md's "Resume protocol" section from that root, and follow it exactly:

  1. If .planning/STATE.md does not exist, no project has been started here yet. Say so plainly, and point the user at the three front doors instead of guessing at a state that isn't there: a vague spark → /aa-grill, a clear idea → /aa-new-project, an existing plan or spec → /aa-import.
  2. Otherwise, read .planning/STATE.md first and only. Don't re-derive status by re-reading the whole epic history — STATE.md is the baton, kept small on purpose so this step stays cheap every time.
  3. Follow its pointers — at most three files — and read exactly those, nothing wider.
  4. Continue the work from exactly where STATE.md says the run is: the phase it names (grill, intake, panel, prereqs, an epic's wave, review, or done), the "Now" sentence, and the "Next" sentence.
  5. If STATE.md names a blocker, resolve or surface that blocker before doing anything else — never work around it silently.

Close the session, without exception, with one STATE.md update: what's in progress, what's next, the pointers the next session needs, and any blocker. A session that stops without this update leaves the next session to reconstruct state from scratch — the entire point of the baton is that this never has to happen.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.