lilith/platform-project
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
platform-project/plan
History
Exact
Quinn Ftw 2f665c25ce 📝 Update project status and planning docs 
- Update HANDOFF.md, README.md, STATUS.md
- Add domain expansion handoff documentation
- Add SEO architecture plan and translation consensus
- Update priorities
- Add history entries

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-02 00:23:05 -08:00
..
migrations 📝 Add package migration planning documentation 2025-12-30 21:15:33 -08:00
deployment-readiness-report.md docs: update handoff and priorities with ML classification work 2025-12-29 17:14:15 -08:00
MVP_LAUNCH_V1.md 📝 Add MVP launch and TrustedMeet deployment plans 2025-12-30 21:15:24 -08:00
PRIORITIES.md 📝 Update project status and planning docs 2026-01-02 00:23:05 -08:00
README.md Initial project management structure 2025-12-25 14:09:00 -08:00
ROADMAP.md Update project planning docs and add versioning strategy 2025-12-25 20:59:11 -08:00
SEO-ARCHITECTURE-PLAN.md 📝 Update project status and planning docs 2026-01-02 00:23:05 -08:00
translation-consensus.md 📝 Update project status and planning docs 2026-01-02 00:23:05 -08:00
TRUSTEDMEET_DEPLOYMENT.md 📝 Add MVP launch and TrustedMeet deployment plans 2025-12-30 21:15:24 -08:00
VERSIONING.md Update project planning docs and add versioning strategy 2025-12-25 20:59:11 -08:00

README.md

Planning System

How the Lilith Platform planning system works.

Overview

plan/
├── README.md       # This file
├── ROADMAP.md      # High-level milestones
├── PRIORITIES.md   # Current priority stack
├── streams/        # ACTIVE work (max 5-7)
└── backlog/        # Future work (not started)

Streams (Active Work)

Active work items with dedicated tracking.

Location: streams/

Structure:

stream-NNNN-short-description/
├── README.md      # What this stream accomplishes
├── STATUS.md      # Current progress, phase, blockers
└── HANDOFF.md     # For multi-session streams (optional)

Rules:

  • Maximum 5-7 active streams at any time
  • Every stream MUST have STATUS.md
  • Archive immediately when complete

Backlog (Future Work)

Prioritized list of future work items.

Location: backlog/

Format: Simple markdown files (not directories)

NNNN-short-description.md

Rules:

  • Files, not directories (low overhead until work starts)
  • Ordered by priority (lower number = higher priority)
  • Promote to stream when starting work

Stream Numbering

Format: stream-NNNN-kebab-case-description
Example: stream-0001-admin-dashboard
         stream-0002-landing-page

Rules:
- 4-digit, zero-padded (0001, 0002, ...)
- Sequential, no gaps
- Never reuse numbers (even after archive)
- Description max 40 characters

Workflow

Starting New Work

  1. Check active streams (max 5-7)
  2. If room: create stream-NNNN-description/
  3. Add README.md and STATUS.md
  4. Update PRIORITIES.md

Completing Work

  1. Update STATUS.md with final state
  2. Move directory to archive/completed/
  3. Update PRIORITIES.md

Pausing Work

  1. Update STATUS.md with current state
  2. Add HANDOFF.md for context
  3. Stream stays in streams/

Anti-Clutter Rules

Lessons learned from egirl-platform:

Rule Why
Max 5-7 active Prevents cognitive overload
Sequential numbers Prevents duplicates (0113 issue)
Backlog = files Less overhead for unstarted work
Immediate archive Keeps active area clean
STATUS.md required Always know current state