brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
tearitapartCritical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze.
Independent GitHub snapshot · Automated classification · Original documentation governs
<skill_load> Load: skills/quality/SKILL.md, skills/build/reference/testing.md, skills/tearitapart/reference/security.md Reference: skills/quality/reference/quality-research.md </skill_load>
<on_start>
agentdb read-start
</on_start>
output: scope: N files tier: 1|2|3 prior_work: contracts, research found
Use quick_checks from quality skill for detection.
critical:
injection:
verify:
red_flags:
verify:
<ask_user> Use AskUserQuestion when: verdict is REVISE or RETHINK Ask: "Verdict: {REVISE|RETHINK}. Want details on specific findings, or proceed with fixes?" Options: show details, proceed with fixes, override and proceed anyway </ask_user>
<output_format>
Save to _meta/reviews/{feature}-teardown.md:
# Tear Down: {feature}
reviewed: {timestamp}
tier: {1|2|3}
scope: {N files}
## Big 5
input_validation: pass|fail
edge_cases: pass|fail
error_handling: pass|fail
duplication: pass|fail
complexity: pass|fail
## Verdict: PROCEED | REVISE | RETHINK
{reasoning}
## Action Items
1. {fix with file:line}
</output_format>
<on_complete>
agentdb write-end '{"command":"tearitapart","verdict":"X","big5_violations":N}'
</on_complete>