Files
support_frontend/.specify/templates/checklist-template.md
T
saqib mirandClaude Sonnet 5 84d26806cf docs: establish supporthub-web constitution v1.0.0
Bootstraps GitHub Spec Kit (scripts, templates, workflow, speckit-*
skills) for this frontend project, mirroring the spec-driven workflow
already used in supporthub-api. Ratifies seven founding principles:
SaaS as the sole identity/access authority, the backend as the sole
source of business logic, strict portal boundaries ((public)/(customer)/
(support)/(admin)), a single typed API client layer (no ad hoc fetching),
configuration over hardcoding for anything the backend exposes as
admin-configurable, an accessible/responsive baseline for an
enterprise all-day tool, and required unit/integration/E2E testing
gates.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-07 10:59:15 +05:30

2.0 KiB

[CHECKLIST TYPE] Checklist: [FEATURE NAME]

Purpose: [Brief description of what this checklist covers] Created: [DATE] Feature: [Link to spec.md or relevant documentation]

Note: This custom checklist is generated by the /speckit-checklist command based on feature context and requirements. Review Ownership: This checklist is a reviewer-owned requirements-quality review artifact. Mark an item [x] only when the reviewer determines the requirements-quality criterion is satisfied. Marker Semantics: [x] means the criterion has been reviewed and satisfied for requirements quality. It does not mean implementation work is complete.

[Category 1]

  • CHK001 First checklist item with clear action
  • CHK002 Second checklist item
  • CHK003 Third checklist item

[Category 2]

  • CHK004 Another category item
  • CHK005 Item with specific criteria
  • CHK006 Final item in this category

Notes

  • Mark items [x] only after review confirms the requirement-quality criterion is satisfied
  • Leave items unchecked when they still require clarification, correction, or reviewer evaluation
  • /speckit-implement reads checklist checkbox state as a gate and must not modify markers
  • checklists/requirements.md has a separate built-in lifecycle maintained by /speckit-specify and /speckit-clarify
  • Add comments or findings inline
  • Link to relevant resources or documentation
  • Items are numbered sequentially for easy reference