docs: add operating cadence and clean styling
This commit is contained in:
@@ -10,6 +10,7 @@ The project has been onboarded to Vikunja and the board now uses the playbook la
|
||||
The next public work is queued as tickets, with `VIK-112` staged as the next active item after the current slice.
|
||||
Implementation tickets are expected to merge back to `develop` first, then hand off into `Ready for Test` / `Deploying to Dev` before Trinity validation and later QA promotion.
|
||||
Any new feature work should also update the Playwright suite so the browser tests become the main regression check as coverage expands.
|
||||
Operating cadence is now defined in `09-operating-cadence-and-batch-plan.md`: Neo pulls the top `Ready for Dev` ticket every hour, posts a completion summary to Discord when finished, Morpheus reviews the lanes every hour, and the ready queue is replenished when fewer than 5 tickets remain unworked.
|
||||
|
||||
## Working Rule
|
||||
|
||||
@@ -25,6 +26,7 @@ We will not build this in one shot. Each numbered document in this folder define
|
||||
6. `06-admin-console.md`
|
||||
7. `07-seo-accessibility-performance.md`
|
||||
8. `08-implementation-plan-and-launch-readiness.md`
|
||||
9. `09-operating-cadence-and-batch-plan.md`
|
||||
|
||||
## Source
|
||||
|
||||
|
||||
Reference in New Issue
Block a user