action-validator
FreePre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
The English summary is being prepared. Showing the original description.
baekenough/second-brain15Updated Oct 8, 2026
FreePublished on GitHub
reasoning-sandwich
Template for pre-reasoning → action → post-verification model allocation
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md2.2 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Reasoning Sandwich Pattern
Purpose
A model allocation pattern that wraps implementation actions with stronger-model reasoning phases. The "sandwich" structure ensures complex tasks get proper analysis before and verification after the core action.
Pattern
[Pre-reasoning] → stronger model (opus)
├── Analyze requirements
├── Identify edge cases
└── Define success criteria
[Action] → balanced model (sonnet)
├── Implement solution
├── Generate code/content
└── Execute plan
[Post-verification] → balanced or lighter model (sonnet/haiku)
├── Verify against criteria
├── Check for regressions
└── Validate completeness
Model Allocation Table
| Phase | Recommended Model | Rationale |
|---|---|---|
| Pre-reasoning (analyze/plan) | opus | Complex architectural reasoning, edge case detection |
| Action (implement/generate) | sonnet | Optimized for code generation, balanced cost |
| Post-verification (review/test) | sonnet or haiku | Structural verification, checklist validation |
When to Apply
| Scenario | Apply Sandwich? | Reason |
|---|---|---|
| New feature implementation | Yes | Needs analysis → code → verification |
| Bug fix with clear root cause | No | Direct action sufficient |
| Architecture decision | Yes | Heavy pre-reasoning, lighter action |
| Batch file edits | No | Mechanical action, no reasoning needed |
| Security-sensitive changes | Yes | Extra verification phase critical |
Integration
This pattern is used by:
structured-dev-cycle— stages map to sandwich phasesevaluator-optimizer— generator/evaluator model selection guidancedeep-plan— research (pre) → plan (action) → verify (post)
Anti-patterns
| Anti-pattern | Problem | Fix |
|---|---|---|
| Opus for everything | Wasteful, slow | Reserve opus for reasoning-heavy phases |
| Haiku for planning | Insufficient depth | Use opus for complex analysis |
| Skipping verification | False completion risk | Always include post-verification phase |
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
adaptive-harness
FreeAuto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
The English summary is being prepared. Showing the original description.
baekenough/second-brain15Updated Oct 8, 2026
Adversarial code review using attacker mindset — trust boundary, attack surface, business logic, and defense evaluation
The English summary is being prepared. Showing the original description.
baekenough/second-brain15Updated Oct 8, 2026
Apache Airflow best practices for DAG authoring, testing, and production deployment
The English summary is being prepared. Showing the original description.
baekenough/second-brain15Updated Oct 8, 2026
Alembic migration patterns for naming conventions, safety checks, expand-contract, env.py configuration, and CI integration
The English summary is being prepared. Showing the original description.
baekenough/second-brain15Updated Oct 8, 2026
ambiguity-gate
FreePre-routing ambiguity analysis — scores request clarity and asks clarifying questions when needed (inspired by ouroboros)
The English summary is being prepared. Showing the original description.
baekenough/second-brain15Updated Oct 8, 2026