Create the deliverable (code, documentation, tests, content) following the user's standards and best practices. Use after validation passes to actually build the work product.
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/22/2026
What it changes
Passed 20 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill91%
Checks it passed that the model alone missed
The deliverable code section uses the header '## The Deliverable'.
The output uses the exact section heading '## Common Patterns Included'.
The response explicitly notes whether any behavioral changes were introduced.
and 3 more in the full report
3 fixed17 passed either way2 still failing0 broke
Pass-rate lift
+14 pp
Tokens
+43%
Agent turns
0%
Response time
+13%
Model gemini-3.6-flashMeasured 8/22/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I've finalized the requirements for refactoring our API authentication service. Please check our project standards and generate the final deliverable. Make sure your response includes a title header, a summary section explaining what was built, bullet points for the principles applied and common patterns incorporated, the complete ready-to-use refactored code, and recommended next steps.
What was checked, without and with the skill
Checked
Without skill
With skill
The response includes the original before code alongside the refactored after code.
Missed
Passed
The response explicitly notes whether any behavioral changes were introduced.
Missed
Passed
The output uses the exact section heading '## Common Patterns Included'.
Missed
Passed
case-01 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md146 linessingle file
Generate Output Skill
Purpose
Transforms validated requirements into actual deliverables (code, documentation, tests, content). This skill follows the user's principles and common patterns defined in their standards.
What to Do
Read the validated requirements from the previous step
Load the project type's standards (from standards.json) to understand their principles and patterns
Generate the deliverable based on:
User's specific requirements
Their saved principles for this project type
Their common patterns (what they always do)
Best practices for this type of work
Follow their patterns - If they defined common patterns, include them:
Example: "Always include error handling" → include it
Example: "Always write JSDoc comments" → include it
Create complete, ready-to-use output
Project Type Specific Guidance
Code Features
Write complete, production-ready code
Include prop types, type annotations, or schema validation
Include error handling
Add comments for complex logic
Include example usage or test case
Follow their coding standards (naming, structure, patterns)
Advanced Git operations and workflows including interactive rebasing, conflict resolution, history manipulation, bisecting for bugs, cherry-picking, reflog recovery, and branch management strategies. Use for: (1) Interactive rebasing and commit cleanup, (2) Complex merge conflict resolution, (3) Git bisect for bug hunting, (4) History rewriting and cleanup, (5) Branch strategy implementation (Git Flow, trunk-based), (6) Recovering lost commits with reflog