CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stress-plan

Use when an implementation plan has just been written and before any code is written — hands the plan to a second model in a fresh context to attack it, then requires every finding to be fixed, rejected in writing, or put to the owner. Invoked by new-feat at the end of its planning step and by orchestrate once per phase, and worth running on its own for any plan whose assumptions have not been checked against the code.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exceptionally well-structured workflow: skip criteria, pre-dispatch checks, a complete copy-paste attacker prompt, a strict finding-closure loop with escalation rules, and re-run criteria, all with explicit validation gates. The main cost is token weight — embedded war stories and rationale paragraphs could be compressed or moved to a reference file to tighten the ~209-line body.

Suggestions

Compress the war stories (the vite minify no-op, the six-apps guard issue, the GDPR erasure batch, the build-directory rejection) into one-line 'e.g.' illustrations of their rules, cutting several hundred tokens from Steps 0-3 without losing the guidance.

Move the full Step 2 attacker prompt checklist and the detailed finding-closure rules (security, bound-exemption, untested-guarantee) into a references/ file, keeping SKILL.md as the overview with the dispatch mechanics and a pointer.

Trim the rationale prose in the opening ('The plan is the one artefact every later step inherits...' paragraph) to the two or three sentences that state the failure mode and why downstream review cannot catch it.

DimensionReasoningScore

Conciseness

The body is mostly efficient operational guidance, but several multi-sentence war stories ('a plan once said to set vite: { build: { minify: true } }...', 'an issue reading "only one of six apps has a guard"...', the rejected-findings build-directory anecdote) and rationale prose could be tightened to one-line illustrations without losing the rule. This matches the 3 anchor's 'mostly efficient but could be tightened' rather than the 4 anchor, where only minor instances of over-explanation remain.

3 / 5

Actionability

The full attacker dispatch prompt in Step 2 is copy-paste ready, and the skill names concrete paths (`.claude/agents/attacker.md`, `docs/superpowers/plans/`, `tools/pr-metrics/index.ts`, `resolveDispatchBranch`), commands (`git grep -w`), labels (`needs:decision`), and exact output formats ('stress-plan: skipped, complexity <n>', 'TASK-BRANCH: <branch>', 'NEEDS INPUT: <question> + options + recommendation'). Fully executable guidance covering the common cases matches the 5 anchor.

5 / 5

Workflow Clarity

Steps 0-4 plus Finish are clearly sequenced with explicit validation gates ('No implementation starts while a finding is open', 'Silence is not a rejection'), a three-outcome closure loop with escalation rules, re-run criteria keyed to plan-shape changes, and a required final verdict format. Clear sequence with explicit checkpoints and feedback loops matches the 5 anchor; the 4 anchor's 'minor validation gaps' does not apply.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is organized into well-signaled sections (## Step 0-4, ## Finish) with content mostly appropriately placed for a single coherent workflow. The ~209-line monolith with the long inline dispatch prompt and multiple anecdotes that could live in a reference file keeps it below the 5 anchor's 'clear overview with well-signaled references'.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it opens with an explicit 'Use when...' trigger, describes the mechanism concretely (second model, fresh context, attack the plan), spells out the three allowed finding outcomes, and defines when to run it standalone. Its only weakness is slightly limited keyword variety (no synonyms like 'plan review' or 'stress-test').

DimensionReasoningScore

Specificity

Names several concrete actions — 'hands the plan to a second model in a fresh context to attack it' and 'requires every finding to be fixed, rejected in writing, or put to the owner' — with minor gaps in coverage. It lists specific actions beyond the 3 anchor's 1-2 but is not the comprehensive multi-action list of the 5 anchor.

4 / 5

Completeness

Explicitly answers both: what ('hands the plan to a second model... to attack it, then requires every finding to be fixed, rejected in writing, or put to the owner') and when ('Use when an implementation plan has just been written and before any code is written', plus standalone triggers). Clear what and explicit when with concrete trigger phrases matches the 5 anchor; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

'Use when an implementation plan has just been written and before any code is written' plus 'plan whose assumptions have not been checked against the code' give good natural keyword coverage. A few natural variants users might say ('plan review', 'stress-test the plan') are missing, keeping it below the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche — pre-implementation plan attack by a fresh-context second model — with distinct triggers, and it names the skills that invoke it (new-feat, orchestrate), so overlap with generic review skills is minimal. Clearly matches the 5 anchor rather than the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

.claude/skills/stress-plan/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.