AGENT SKILL

pending

List what waits on the user (drafts in plans/drafts/, stubs, unpushed branches, draft PRs) and archive a finished draft

License 许可
MIT
最近更新
2026-11-13
Stars
★ 1
Forks
0

01 前言 Front Matter

name
pending
description
List what waits on the user (drafts in plans/drafts/, stubs, unpushed branches, draft PRs) and archive a finished draft
argument-hint
[done <file> | stub <action>]
disable-model-invocation
true

03 SKILL.md 正文

Plugin root: ${CLAUDE_PLUGIN_ROOT}. Use this absolute path wherever shared files say <plugin>; the variable is not set in Bash.

You keep the user's waiting list honest: it is read from the work itself, never written by hand.

Iron laws

  1. The list comes from pending.mjs; never keep a second list by hand, because a copy drifts from the files it describes.
  2. A draft leaves plans/drafts/ only through pending.mjs done, after the tool that published or applied it confirms the result, or after the user drops it.
  3. Archiving is local; it never publishes, pushes or changes a tracker.

Not this skill

Posting a review draft → /tedy:review-pr. Posting Doc or Figma comments or tracker drafts → /tedy:pm.

Procedure

  1. List. From the project directory: node ${CLAUDE_PLUGIN_ROOT}/scripts/pending.mjs list. Quote its output; it prints Nothing waits on the user. when the list is empty. Done when the output is in the reply.
  2. Done. For done <file>: confirm the item was posted, sent, applied or dropped (the posting tool's output, a comment list or a tracker read-back), then node ${CLAUDE_PLUGIN_ROOT}/scripts/pending.mjs done <file> and report the archived: path. Done when the file sits under plans/archive/ and MOVES.tsv has its line.
  3. Stub. For an item with no file and no git trace (a message the user must send, a call to make): node ${CLAUDE_PLUGIN_ROOT}/scripts/pending.mjs stub "<action>". Done when the printed file exists.

Done

The reply quotes the current list, and every archived or stubbed file path is named.

04 同仓库更多 Skills

Tedydev-web
Tedydev-web/tedy-kit

setup

Build or update the project map that /tedy skills read (repositories, PRD tabs, Figma nodes, tracker, languages) through guided questions. Use when a /tedy skill reports no map or a missing field, or when the user wants to change one.

★ 1
Tedydev-web
Tedydev-web/tedy-kit

review-pr

Review a teammate's pull request against the PRD, Figma and the backend or contract code, draft line-by-line hints in the user's style and the map's review language, and post them only after the user approves. Use for "review PR", "review pull request" or the same request in any language, a pasted PR link, and for any request about an existing review draft (plans/drafts/review-*-line-comments.md), such as showing it for approval, trimming or rewording a comment, posting it, or checking replies. Not for reviewing your own branch before opening a PR; that is /tedy:dev.

★ 1
Tedydev-web
Tedydev-web/tedy-kit

reconcile

Cross-check one scope (an epic, a use case, a rule in words, or a PR) across the PRD, Figma, backend, contract, frontend and PM demo into a mismatch table with a raise list. Use when the user asks to reconcile or cross-check the PRD against code.

★ 1
Tedydev-web
Tedydev-web/tedy-kit

pm

Work as the project's PM in the user's style - turn a reconcile into a gaps ledger, draft Google Doc and Figma comments and OpenProject tasks, post them after approval, and check replies. Use when, in any language, the user asks to create or change tracker tasks (status, assignee, estimate, rollback), comment on the PRD Doc or Figma, check replies, or cross-check the PRD against Figma for the PM. Not for writing code.

★ 1
Tedydev-web
Tedydev-web/tedy-kit

dev

Implement one tracker task end to end in the user's style (reconcile its scope, build, verify on the commit, independent review, commit) or rebut an external review (Gemini, bots, colleagues) claim by claim. Use for "implement task 21298", "implement", "fix per the task" in any language, or a pasted external review of the user's own PR.

★ 1