Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation, especially for multi-module work, unclear acceptance criteria, or architecture-heavy requests.
SkillScore82Maintained
Automatic
◆Product Management pack
Last verified 8/9/2026
What it changes
Passed 18 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill82%
Checks it passed that the model alone missed
Refuses to fetch remote skill files over HTTP.
Formats criteria in EARS pattern using 'shall'.
Avoids standard Gherkin Given/When/Then syntax.
and 12 more in the full report
11 fixed7 passed either way4 still failing0 broke
Pass-rate lift
+50 pp
Tokens
-1%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/9/2026v218 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Write an acceptance criterion for a scenario where an admin user attempts to delete an active account during maintenance mode.
What was checked, without and with the skill
Checked
Without skill
With skill
Formats the acceptance criterion using EARS clause syntax.
Missed
Passed
Includes system response statement containing 'shall'.
Missed
Passed
case-16 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md154 linessingle file
Sibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
Spec Workflow
Activation Contract
Use this first when
The request is a new feature, multi-step product change, cross-module integration, or architecture/design task.
Acceptance criteria are unclear and need to be made explicit before implementation.
The work involves multiple files, user flows, database design, or UI design that needs staged confirmation.
Read before writing code if
You are unsure whether the task should go straight to coding or should first go through requirements, design, and task planning.
The request mentions a new page, a new system, a redesign, a workflow, or a multi-module refactor.
Then also read
Frontend page or visual design work -> ../ui-design/SKILL.md
Advanced data-model work -> ../data-model-creation/SKILL.md
Do NOT use for
Small bug fixes with clear scope.
One-file documentation updates.
Straightforward config changes.
Tiny refactors where the user already gave exact implementation instructions.
Common mistakes / gotchas
Jumping into coding before acceptance criteria are explicit.
Skipping user confirmation between requirements, design, and tasks.
Writing vague tasks that do not map back to user-visible outcomes.
Treating UI work as purely technical implementation without clarifying design intent.