{"id":"mkt2-great-for-not-a-fit-section","audience":"marketing","category":"social-content","track":"marketing","technique":"grounding","level":"intermediate","title":"Write a Great for and Not a fit section that admits limits","free":false,"task":"Stackline is a project tool, and the landing page will get an honest fit section. Write a prompt for plain text with two headings in capitals, GREAT FOR and NOT A FIT, with at most 3 dash bullets under each, each bullet 12 words or fewer, six bullets at most in total. Every NOT A FIT bullet must start with \"No \" and every GREAT FOR bullet must start with a verb. Use only the spec, and if a feature is only planned, treat it as not available.","materialLabel":"Product spec (attached to your prompt automatically)","material":"STACKLINE - fit notes from product and support\n\nBest results: teams of 5 to 50 who run recurring projects (monthly campaigns, weekly releases) and want templates for them. Shared task boards, recurring task templates, and comments on tasks are shipped.\nNot supported today: single sign-on (SSO), time tracking, Gantt charts, and a self-hosted option.\nPlanned: time tracking (Q3 next year), SSO (not scheduled).\nSolo users: possible, but there is no solo plan; the minimum is 3 users.\nSecurity: data stored in the US; encrypted at rest.\nSales wishlist for the page: \"works for any team of any size\", \"all the features you need\".","rules":[{"type":"plainText"},{"type":"maxBullets","max":6},{"type":"maxWords","max":90}],"mistakes":[{"title":"Saying it fits everyone","why":"The AI picks up the sales wishlist.","fix":"Say: \"Use only the spec; no 'any team of any size'.\"","checks":["r2"]},{"title":"Hinting at roadmap items","why":"The AI says time tracking is 'coming soon'.","fix":"Say: \"Treat planned features as not available.\"","checks":["r1","r2"]},{"title":"Too many bullets","why":"Sections turn into long lists.","fix":"Say: \"At most 3 bullets per heading, 12 words each.\"","checks":["r0","maxBullets"]},{"title":"Letting markdown through","why":"AI adds bold text and headings by default.","fix":"Add: \"Plain text only, no bold, no headings.\"","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and often runs past a word limit.","fix":"Cap each part (for example \"each line under 15 words\") so the total lands well under the limit.","checks":["maxWords"]}],"promptHints":[{"label":"Gives both headings","patterns":["great for.*not a fit"]},{"label":"Caps bullets","patterns":["3 (dash )?bullets","three (dash )?bullets","at most 3"]},{"label":"Treats planned as unavailable","patterns":["planned","not available","only planned"]},{"label":"Uses only the spec","patterns":["only the spec","spec only","nothing (else|outside)"]},{"label":"Caps bullet length","patterns":["12 words"]}],"hint":"An honest fit section names real limits. Give the headings, the bullet caps and how to treat planned features.","mission":"Write an honest fit section for Stackline's landing page.","musts":["NOT A FIT starts No","Planned means unavailable","Spec facts only"],"rubricLabels":["The output has the headings GREAT FOR and NOT A FIT with at most 3 dash bullets under each, each under 12 words or fewer","Every GREAT FOR bullet starts with a verb and every NOT A FIT bullet starts with No; GREAT FOR uses facts such as teams of 5 to 50, recurring projects, templates or shared boards, and NOT A FIT names at least SSO and time tracking","It does not say it works for any size of team, does not say time tracking or SSO is coming, and adds no features not in the spec"]}