Skip to content

Plans

Implementation plans for upcoming features. A plan is a working document — it captures the goal, approach, open questions, and files affected before any code is written, so the implementing agent (or human) has a clear contract.

Conventions

  • File name: kebab-case feature name, e.g. login.md.
  • Sections: Goals, Out of scope, Approach (split into backend and frontend subsections), Open questions, Risks, Files affected.
  • Plans cover both backend and frontend. Every plan must explicitly address what happens on the .NET API and the React SPA. If one side has no work, write "Backend impact: none" / "Frontend impact: none" — the omission must be intentional. (See CLAUDE.md → "Plans cover both backend and frontend.")
  • Status values: Proposed → In progress → Implemented (with link to commit/PR) or Abandoned.
  • Plans are not historical artifacts — when a feature ships, mark it Implemented and link to the ADR or PR; do not delete.
  • If a plan's Open questions resolve into project-level decisions, promote them to ADRs in wiki/adr/.

Index

  • Login — controller-based switch + first models (User, EmailAuthentication) + signup/verify/sign-in endpoints.