Saucebox Registry
← Browse

@tiann/execplan

B

When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.

skillclaude

Install

agr install @tiann/execplan --target claude

Writes 2 files into .claude/skills/, pinned to git-9b1f4b2f.

  • .claude/skills/execplan/README.md
  • .claude/skills/execplan/SKILL.md

Document

name: execplan description: When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.

Create an execution plan following PLANS.md methodology.

Instructions

  1. Read PLANS.md first - This contains all methodology, requirements, structure, and guidelines
  2. Follow the process and skeleton defined in PLANS.md to the letter

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-9b1f4b2f26ac2026-07-30