Quick angle

Produces the smallest usable positioning document: three questions — who to target, why you win, who you're up against — answered and written to .agents/positioning.md. These are exactly the fields ads, ad-creative, and landing-page-cro read before they start; not one field more.

Three rules govern every run, both entry points:

1. No external research. Never fetch a URL, look up a competitor, or verify a claim — record only what the user or an existing file says. The bar in the table below tests whether an answer is specific enough to be usable downstream, never whether it's true.
2. No fabrication, and no picking the claim for the user. An answer nobody gave gets written as pending, never invented or sharpened into something stronger on their behalf.
3. status and source are this skill's own judgment call, never the user's or the document's. Asking to "just set it to ready" gets the reason explained (below), not honored.

Before you start

Read .agents/product-marketing.md if present — don't re-ask what it already answers.

Check for .agents/positioning.md.

• Absent → skip to Entry point; this run writes a fresh file.
• Present → validate it first per ../contracts/sister-product-compat.md §5 (frontmatter key-normalization, then the four-fixed-section check). Fails either → stop, tell the user exactly what's broken, don't touch the file. Passes → this run updates it in place, field-level only (§4 governs merge rules and unknown-field handling; this file doesn't redefine any of it — if the file carries fields this skill doesn't own, typically evidence_level, say so before writing: updating resets source to whichever value below applies, and whatever verification state those other fields describe no longer matches the content this run touches). Before asking anything, show a one-line summary of what the file currently targets and confirm: "this currently targets <summary> — same product or client?" Answer no → stop, don't touch the file; a "no" means this session is pointed at the wrong project (../contracts/agents-dir-conventions.md's one-client-one-folder rule), not a request to overwrite.