mirror of
https://github.com/pbakaus/impeccable.git
synced 2026-09-12 06:06:37 +03:00
51e5af258e
* Add positioning and conversion questions to init flow Expand init.md so PRODUCT.md captures audience splits, positioning, and brand-register conversion/proof context before design work starts. Co-authored-by: Cursor <cursoragent@cursor.com> * Fix init over-inference by raising the evidence bar for skipping questions. Sparse repos were letting the model treat weak guesses as settled answers; Step 3 now asks unless the codebase provides strong, explicit evidence. Co-authored-by: Cursor <cursoragent@cursor.com> * Improve init interview order and PRODUCT.md proof output shape. Ask positioning in round 1, actively collect proof assets, and give Proof & conversion a plain bullet skeleton so generated PRODUCT.md stays lean. Co-authored-by: Cursor <cursoragent@cursor.com> * Fix init interview bundling and write-time padding, verified via harness runs Co-authored-by: Cursor <cursoragent@cursor.com> * Revert init reference follow-up rule to advisory wording on line 88 Co-authored-by: Cursor <cursoragent@cursor.com> * Tighten init interview rules after harness runs: split register, options, prose Settle split register before brand-only questions, require standalone emotions and confirmed secondary audiences, forbid compound options, and keep PRODUCT.md bold minimal. Co-authored-by: Cursor <cursoragent@cursor.com> * Ask brand-register init questions in magazine-editor voice, no skill jargon Co-authored-by: Cursor <cursoragent@cursor.com> * Fix init chat fallback to ask one question at a time When no structured question tool exists, init should ask in chat with lettered options and wait for each answer instead of dumping a list. Co-authored-by: Cursor <cursoragent@cursor.com> * Resolve init review comments: split purpose question, gate template section Purpose and success are now separate questions, and docs-stated purpose is framed as a hypothesis below the strong-evidence bar rather than a competing always-ask rule. The PRODUCT.md template now tells product register to omit the Conversion & proof section including its heading. Co-authored-by: Cursor <cursoragent@cursor.com> * Keep belief-sequence question out of skill jargon Ask what visitors must believe in plain words; map the answer to the template belief ladder in a parenthetical instead of leading with the term. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Abdul Wahab <abdulwahab@Abduls-MacBook-Pro-2.local>