docyrus-project-planning
Docyrus Project Planning
A repo-local planning system (docyrus project-plan) that tracks phases, features, and tasks for a Docyrus-backed application. It lives in docyrus/project-plan/ and renders PROJECT_PLAN.md (human view) from project-plan.json (source of truth), alongside a diagrams/ folder of author-owned Mermaid diagrams.
Use it to design the application before writing code — data model first, then the navigation/layout shell, then real UI content topic by topic, then the cross-cutting backend (dashboards, templates, ACL, automations, AI tools).
For platform capabilities, see the docyrus-platform skill. For CLI flags, see the docyrus-cli-app skill and references/command-reference.md.
Concepts
| Entity | Description |
|---|---|
| Phase | A lifecycle stage (e.g. "Data Sources", "Navigation & Layout", a per-topic UI phase). Groups tasks by when they are done. Phases are ordered. |
| Feature | A coherent unit of functionality (e.g. "Invoices data source", "Deals kanban board"). Spans phases via its tasks. Versioned when redesigned. |
| Task | An atomic work item inside a feature. Has a type, assignee (agent/user), and status. |
Task types: new-implementation, bug-fix, work, api-test, browser-automation-test
Task statuses: planned → in_progress → done (or blocked)