forge

Forge

Critical — Adversarial verification

Verify consequential findings and decisions before acting on them.

• Seek counterexamples and independent evidence for load-bearing or contested claims. Use fresh reviewers when available and useful; label sequential self-review as less independent.
• Resolve material findings by correction, evidence-backed refutation, or an explicit remaining risk. Never silently drop them.
• Evidence decides, not reviewer counts or confidence alone. One reproducible defect can invalidate a conclusion.
• Scale verification to the stakes. Keep settled facts settled and reversible, low-impact checks light.

Important — Writing rules

Apply these rules to emitted prose: docs, comments, commit messages, PR bodies, and release notes.

• Match surrounding punctuation, capitalization, and formatting.
• Every sentence changes the reader's understanding. Cut it otherwise.
• Lead with the action or outcome.
• Use concrete language and lists when they improve comparison or sequence.
• Assert positively. Reserve negation for real constraints (NEVER commit secrets).
• No marketing words: powerful, robust, seamlessly, leverage, unlock, comprehensive, delightful.
• No AI tells: delve, tapestry, intricate, pivotal, testament, underscore, crucial, garner, showcase, additionally, moreover, furthermore, indeed.
• For substantive English prose, use /humanize-en if installed with the existing scope and authorization. It adds no approval stage; skip redundant passes over short status text.

Pre-implementation thinking for: $ARGUMENTS

Objective

Research the question, challenge competing approaches, and emit one decision or implementation plan. Decide routine reversible details, surface consequential tradeoffs, and escalate user-owned choices. Preserve existing build authorization and explicit planning checkpoints.