Website Project Scope: MVP Checklist + Risk Map

Building a client website? → Website Project Scope Building an app? → App MVP Scope

Website project scope and requirements from a client brief: flags missing info instead of guessing, splits MVP vs later, rates P0-P2 risks and ships an MVP checklist with acceptance criteria.

Unlike generic "plan my website" prompts, this skill flags what your brief is missing instead of inventing requirements, draws a hard MVP-vs-Later line, and rates delivery risks P0 to P2. No invented timelines, budgets, rankings or conversion promises.

Sample output (excerpt — Harborline Tools brochure site, Generated: 2026-10-16):

P0 · Forms · CRM integration fields not supplied — confirm before build P1 · Performance · Hero video may blow LCP on mobile — plan poster + lazy load Acceptance check: visitor can submit contact form and appear in CRM within 5 minutes

Works in Claude Code, Cursor and Codex · evidence-only scope · v1.1, updated Oct 2026 · questions answered via Agensi messages · More Cygnix Labs tools: https://apify.com/cygnix_labs

The problem Web projects slip because nobody agreed what ships first. Turn a user-supplied website brief, sitemap, Figma, repo notes, or live URL notes into a concise, evidence-led scope audit. Focus on MVP boundaries, stack fit (WordPress, React, Next.js, Webflow, or hybrid), core pages and flows, performance and SEO readiness, and a testable next-step checklist. This is a scoping template and checklist, not a build quote, traffic guarantee, or SEO ranking promise. Use only facts and artefacts supplied by the user; never promise rankings, conversions, or fixed delivery dates.

What it does

• Feature Triage Categorizes every requested page and flow into MVP must-haves versus post-launch enhancements with clear technical rationale.
• Stack Analysis Evaluates the implications of using WordPress, React, Next.js, or Webflow based on the specific feature set and integration needs.
• Risk Identification Flags high-friction areas like custom admin roles, real-time data, or complex animations that typically cause timeline slippage.
• Evidence Gap Mapping Explicitly labels missing information in the brief, such as hosting constraints or accessibility requirements, to prevent assumptions.
• Actionable Scaffolding Generates a P0/P1/P2 priority findings table and a concrete acceptance checklist for the initial build phase.

How it works

1. Provide the agent with your project brief, sitemap, tech stack preference, or Figma notes.
2. The agent analyzes the inputs to separate stated goals from unverified assumptions.
3. It generates a Markdown audit report including a scoped MVP boundary table and a risk assessment.
4. Review the "Not supplied" section to identify exactly what technical or business details you need to chase next.

Frameworks & tools

Optimized for projects using WordPress, React, Next.js, Webflow, and common integrations like Stripe, HubSpot, or Firebase.

Why this beats prompting it yourself

Generic prompts often produce "yes-man" summaries that agree with every feature request. This skill enforces a strict evidence-led framework that proactively hunts for scope risks and forces a distinction between MVP and polish.

Use cases

• Auditing a client's initial RFP to identify hidden technical complexities.
• Refining an internal product roadmap to define a true version 1.0.
• Creating a technical pre-flight report before starting a sprint.

Known limitations

Does not provide financial quotes or calendar timelines. Requires human verification for SEO and performance claims as it cannot browse live authenticated environments.

Next steps

• App MVP Scope — Feature Priority + Risk Checklist (mobile projects)
• Chatbot Script Builder — Intents to MVP Conversation Flow
• Launching content after the build? SEO Content Brief (free) → Topical Authority Map