01 — Requirements and Planning Checklist#

Verify that the project solves a validated problem, has measurable goals, clear scope, testable requirements, realistic delivery plans, and defined API/frontend requirements.

Scope: Frontend-specific. This file is one part of the 01_Requirements_and_Planning.md checklist. Apply the domain-wide release gate across all applicable scope files; each checklist ID remains unique.

Review details#

• Project / product:
• Release / version / environment:
• Scope and applicable jurisdictions / markets:
• Reviewer / owner:
• Review date:
• Decision: Pending / Approved / Approved with documented exceptions / Blocked

How to use#

1. Copy this reusable checklist into project-specific review records; leave the shared template unchecked.
2. Mark [x] only after verifying a check with a linked requirement, decision record, research finding, or other evidence. Record failed or inapplicable items (including N/A rationale) in project-specific review notes or an issue tracker, keyed by REQ ID.
3. Assign owners and deadlines for unclear requirements, unvalidated assumptions, unresolved dependencies, and other blockers.
4. Review the plan when the project scope, audience, API contracts, interface requirements, or external constraints change. These checks support project planning; they do not replace expert legal, security, or accessibility review.

Frontend Checks#

• REQ-071 Identify all user roles, primary journeys, entry points, and device/browser support targets.
• REQ-072 Specify navigation hierarchy, page states, deep-link behavior, and important content requirements before implementation.
• REQ-073 Define acceptance criteria for forms, field validation, error recovery, confirmation, and prevention of duplicate actions.
• REQ-074 Include explicit loading, empty, permission-denied, offline, timeout, and partially unavailable states in user flows.
• REQ-075 Document applicable accessibility target (for example WCAG 2.2 AA) and include keyboard, assistive-technology, contrast, and focus requirements.
• REQ-076 Plan responsive breakpoints and interaction behavior for keyboard, mouse, touch, and small-screen use.
• REQ-077 Define localization needs including languages, time zones, dates, numbers, currencies, and directionality.
• REQ-078 Identify authentication, account-switching, session-expiry, and protected-route experiences.
• REQ-079 Specify frontend data needs and align each essential field or state to an API contract or other data source.
• REQ-080 Set measurable frontend performance budgets or targets, including key page templates and devices.
• REQ-081 Agree analytics events, meaningful conversions, privacy-consent dependencies, and responsible data owners.
• REQ-082 Plan prototype/usability feedback with representative users before finalizing high-risk workflows.
• REQ-083 Define content ownership for interface copy, help text, errors, legal notices, and accessibility labels.

Release gate#

• The scope, objective, target users, and success criteria have been reviewed and approved by the accountable product owner or sponsor.
• All release-critical requirements have unambiguous acceptance criteria, identifiable owners, and a feasible verification approach.
• High-impact assumptions, dependencies, external approvals, constraints, and delivery risks are resolved or have explicitly accepted, time-bound mitigation plans.
• API and frontend requirements are agreed by relevant consumer/provider and user-experience owners, or documented as genuinely not applicable.
• The delivery plan has an accountable owner, realistic milestones, a process for changes, and explicit readiness/sign-off responsibilities.

Domain-specific approval rule: Do not approve a release plan with undefined success criteria, conflicting critical requirements, unowned blocking dependencies, or unapproved material scope or risk decisions. A planning sign-off is not proof that implementation or release tests have passed.

Trusted references and scope#

The checklist translates the following primary guidance into project-planning verification tasks; it does not reproduce the referenced standards or imply formal certification.

• NASA Systems Engineering Handbook — requirements definition — clear, traceable, feasible, verifiable requirements and design constraints.
• NASA Systems Engineering Handbook — requirements quality and traceability — uniqueness, consistency, testability, and verification planning.
• GOV.UK Service Manual — learning about user needs — evidence-based needs and traceability into delivery work.
• GOV.UK Service Manual — performance metrics — purpose, benefits, measurements, and iteration.
• GOV.UK Service Manual — deciding on priorities — transparent prioritization across features and other work.
• The Scrum Guide (2020) — product goal, product backlog, and definition of done (use if relevant to the team's delivery method).
• OpenAPI Specification 3.2.1 — standard interface description for HTTP APIs (when applicable).
• W3C — WCAG 2.2 — testable web accessibility criteria (when applicable).

Applicability: Requirements management practices vary with project size, industry, development method, and jurisdiction. Do not automatically impose Scrum or government-service requirements on other teams; tailor the controls to actual risks and users.

Source review date: 2026-11-12.

Suggested testing tools#

Choose tools appropriate to the project's stack and risks; automation supports evidence but does not approve the checklist.

• Test focus: acceptance criteria, negative scenarios, and scope changes; include browser and client behavior where applicable.
• Cross-stack: Cucumber + Playwright.
• Python: pytest-bdd + pytest; for pytest-based suites, run python -m pytest -q.
• TypeScript: Cucumber.js + Playwright + Vitest; for Vitest-based suites, run npx vitest run (or npx playwright test for E2E).
• JavaScript: Cucumber.js + Playwright + Jest; for Jest-based suites, run npx jest --ci (or npx playwright test for E2E).
• Evidence: Save tool versions, configuration, test environment, fixtures, results, and links in project-specific review records using the existing checklist IDs. Expert review remains necessary where relevant.

Suggested AI skills for verification#

These are optional agent review aids, not automated passes or release approval. Each linked repository had at least 1,000 GitHub stars when checked on 2026-11-12; counts are per repository, not per skill, and do not indicate security or correctness.

• spec-driven-development — Check requirements against executable acceptance criteria (addyosmani/agent-skills, 116,378 repo stars).
• writing-plans — Identify missing verification steps and owners (obra/superpowers, 316,578 repo stars).
• breakdown-test — Derive negative and edge-case test scenarios (github/awesome-copilot, 41,073 repo stars).

How to check: In a project-specific copy, have the agent audit the frontend scope and map findings to this file's existing checklist IDs, with code/configuration references, reproducible test results, failed or inapplicable cases, and uncertainties. Independently verify findings; keep shared template boxes unchecked and retain human approval requirements.

Before use: Read the skill's SKILL.md, referenced scripts, license, and requested tool permissions. Only execute vetted skills with appropriate access in a controlled environment.

Important warning: reference only#

⚠️ Reference only — not a definitive or exhaustive checklist. This template is a starting point for review, not the ultimate authority or a guarantee of project safety, quality, regulatory compliance, accessibility, security, or launch readiness.

Use project-specific judgment and independent verification. Requirements and risks evolve and differ by project, technology, and jurisdiction. Adapt the checks, consult current authoritative sources, perform relevant tests, and obtain qualified specialist review or approval when appropriate. Checking every box does not replace these steps.