Files

Knee Cola 57dcebd640 refactor: convert repository to monorepo with npm workspaces

Restructured the repository into a monorepo to better organize application code
and maintenance scripts.

## Workspace Structure
- web-app: Next.js application (all app code moved from root)
- housekeeping: Database backup and maintenance scripts

## Key Changes
- Moved all application code to web-app/ using git mv
- Moved database scripts to housekeeping/ workspace
- Updated Dockerfile for monorepo build process
- Updated docker-compose files (volume paths: ./web-app/etc/hosts/)
- Updated .gitignore for workspace-level node_modules
- Updated documentation (README.md, CLAUDE.md, CHANGELOG.md)

## Migration Impact
- Root package.json now manages workspaces
- Build commands delegate to web-app workspace
- All file history preserved via git mv
- Docker build process updated for workspace structure

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2025-12-25 12:13:04 +01:00

3.0 KiB

Raw Permalink Blame History

📑 Sprint Playbook Template

0. Sprint Status

Status: [🔲 not started | 🚧 in progress | 🛠️ implementing <user story id> | ✅ done]

1. Sprint Metadata

Sprint ID: [unique identifier]
Start Date: [YYYY-MM-DD]
End Date: [YYYY-MM-DD]
Sprint Goal: [clear and concise goal statement]
Team/Agent Responsible: [AI agent name/version]
Branch Name (Git): [feature/sprint-]

2. Current State of Software

(Concise snapshot of the project before Sprint work begins)

Main Features Available: [list]
Known Limitations / Issues: [list]
Relevant Files / Modules: [list with paths]
Environment / Dependencies: [runtime versions, frameworks, libs]

3. Desired State of Software

(Target state after Sprint is complete)

New Features: [list]
Modified Features: [list]
Expected Behavior Changes: [list]
External Dependencies / Integrations: [list]

4. User Stories

Each story represents a unit of work that can be developed and tested independently.

Story ID	Title	Description	Acceptance Criteria	Definition of Done	Assignee	Status
US-1	[short title]	[detailed description of functionality]	[conditions for acceptance]	[implemented, tested, docs updated, lint clean]	[AI agent]	🔲 todo
US-2	...	...	...	...	...	🔲 todo

Status options: 🔲 todo, 🚧 in progress, 🚫 blocked, ✅ done

5. Technical Instructions

(Guidance to help AI converge quickly on the correct solution)

Code Snippets / Patterns:

# Example placeholder snippet
def example_function():
    pass

Architecture Guidelines: [layering, module boundaries, design patterns]
Coding Style Conventions: [naming rules, formatting, linting]
Testing Strategy: [unit/integration, testing framework, coverage target]

6. Risks and Dependencies

Risks: [list potential blockers, e.g., API instability, missing test coverage]
Dependencies: [other modules, external services, libraries, team inputs]

7. Sprint Definition of Done (DoD)

The Sprint is complete when:

AI-Responsible Items (AI agent can verify and tick):

All user stories meet their individual Definition of Done.
Code compiles and passes automated tests.
Code is committed and pushed on branch [feature/sprint-<id>].
Documentation is updated.
Sprint status updated to ✅ done.

User-Only Items (Only user can verify and tick):

Branch is merged into main.

3.0 KiB Raw Permalink Blame History