implement-feature

To plan and implement a full-stack feature, use a triple-verified workflow that coordinates frontend and Convex backend development through structured planning, schema alignment, and three validation passes to ensure high-quality delivery.

The triple verification process validates a feature implementation plan across three distinct passes, checking against the codebase, dependencies, and risks to ensure feasibility and alignment before any code is written.

To enforce schema-first development and auth guards in Convex, apply a disciplined workflow that requires strict schema alignment and authentication validation during the backend implementation phase before frontend integration.

When implementing a feature, you need to create a PLAN_[FEATURE_NAME].md file, a BUGS_[FEATURE_NAME].md file, backend and frontend modules, and translations, ensuring all paths and function names are concrete and release-ready.

This structured implementation workflow is designed for significant features or UI components that touch both backend and frontend code, making it excessive for minor updates that do not require cross-team coordination.

Yes, the feature implementation workflow enforces regression checks before delivery, ensuring end-to-end discipline through consistent naming, auth guards, and validation passes to mitigate risks.