forgelisted

# Forge <!-- canonical:writing-rules:start --> ## Important — Writing rules These rules govern every prose artifact this skill emits — READMEs, CHANGELOGs, commit messages, PR bodies, release notes, doc paragraphs, non-trivial comments. Apply them at draft time, verify before output. - Match the surrounding style — punctuation, capitalization, backtick conventions, em-dash vs parens, bullet style. - Every sentence changes the reader's understanding. Cut it otherwise. - Front-load the verb — "Creates", not "This helps you create". - Concrete over abstract. Lists for ≥3 enumerable items. - 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. - After drafting English prose, invoke `/humanize-en` if installed. <!-- canonical:writing-rules:end --> Pre-implementation thinking for: $ARGUMENTS ## Objective Take any starting point — a question, a rough idea, a brainstorm, a GitHub issue — research it wide, stress-test the options, decide every call inside the engineering mandate, and emit one artifact `/apex` can build from. Forge is the "think" half; `apex` is the "build" half. The seam between them carries the one human checkpoint that matters: review the plan before any code. The discriminator is the Decid