Validate a project spec against the schema and return structured issues. A project spec: name, overview, target_audience, platforms[], tech_stack[], features[] ({title, description, priority: must-have|nice-to-have|future, acceptance_criteria?[]}), screens[]? ({name, purpose}), data_model[]? ({entity, fields[]: {name, type, notes?}}), constraints[]?, non_goals[]?, revenue_model?. Checks for missing/empty required sections, placeholder text (e.g. "TBD", "lorem ipsum", "fixme"), and features without a priority — all reported as errors. Also returns non-blocking quality hints, e.g. "none of your must-have features have acceptance_criteria" or "no non_goals listed".

Render a project spec into a deterministic, Draftlytic-style Markdown PRD. A project spec: name, overview, target_audience, platforms[], tech_stack[], features[] ({title, description, priority: must-have|nice-to-have|future, acceptance_criteria?[]}), screens[]? ({name, purpose}), data_model[]? ({entity, fields[]: {name, type, notes?}}), constraints[]?, non_goals[]?, revenue_model?. Output includes: title, overview, target audience, platforms, tech stack, features grouped by priority (must-have / nice-to-have / future) with acceptance-criteria checklists, screens & navigation, data model tables, constraints, and non-goals. Run validate_spec first — this tool renders whatever it's given, even an incomplete spec.

Return a planning checklist grouped by category (platform, tech stack, target audience, features, competitors, revenue, constraints, data model, notifications, external services, design & UX), each with 2-4 concrete questions. Use this to interview the user before drafting a spec — you don't need to ask every question, just enough per category to fill in the schema meaningfully.

Build a link that opens this idea in the full Draftlytic app (free account, no card), which runs its own guided flow: AI-tailored questions, full project generation, an editable structured spec, and PRD export (plus scan-for-gaps, logo drafts, and GitHub push on paid plans). Pass either the spec drafted here (it gets compressed into a starting brief) or a plain-text idea. Show the returned URL to the user as a clickable link — this tool only builds it; nothing is sent anywhere.