Best next agent request
Work through the urgent MVP stabilization list.
Start the next substantive work on a feature branch from updated main.
30-second project scan
MVP app exists. Stabilization continues.
A React/Vite app branded publicly as Sleeping Bunnies. The useful PM view is: Help families understand child sleep patterns without making the app feel clinical. Main blocker: Urgent fixes and manual QA.
- Project stage
- MVP stabilization
- Main blocker
- Urgent fixes and manual QA
- Business goal
- Help families understand child sleep patterns without making the app feel clinical
- Docs health
- 6 docs need review
Do not delegate yet
Premature advice, monetization, or future scope.
Do not add medical-sounding advice, opaque sleep claims, monetization, or roadmap features before urgent fixes and manual QA are handled.
Milestone Gates
What has to become true before the next milestone
These are delegation checkpoints for a nontechnical project manager.
Gate 1
Project direction
Confirm the business goal and current stage before assigning new work.
Ask: restate the project direction in plain language.Gate 2
Source freshness
Check whether active docs are current, missing, or old but quiet.
Ask: list source docs that need attention.Gate 3
Main blocker
Identify the blocker that prevents the next milestone from being treated as done.
Ask: explain the main blocker and evidence.Gate 4
Safe next request
Choose one agent request that moves the project without crossing authority boundaries.
Ask: propose the smallest safe next task.Gate 5
Validation proof
Name the checks or reviews needed before claiming the work is complete.
Ask: prepare validation evidence.Gate 6
Avoid list
Keep unsafe, premature, or out-of-scope work visible before delegation.
Ask: summarize what not to delegate.Work Lanes
Where the office PM can point agents
Each lane turns project state into a safe, plain-language request.
Urgent fixes
Known product and UX gaps
The next useful work should reduce friction in the current MVP.
Ask an agent: Read urgent fixes and pick the smallest safe implementation slice.
Avoid: Jumping to monetization or deep analytics before core trust is stable.
Core sleep workflows
Logging, timeline, dashboard, exports
The core family workflow exists but still needs polish and validation.
Ask an agent: Prepare a focused QA pass for sleep logging and daily review flows.
Avoid: Changing data meaning without checking downstream screens.
Pattern insights
Readable summaries and transparent logic
Insights should stay lightweight and explainable.
Ask an agent: Review pattern-engine roadmap and suggest the next transparent insight improvement.
Avoid: Adding opaque advice or medical-sounding claims.
Manual QA
Mobile behavior, browser checks, edge cases
Manual QA remains important before broader release confidence.
Ask an agent: Run or prepare the manual QA checklist for the current MVP surfaces.
Avoid: Calling the app release-ready from helper tests alone.
Roadmap
Family feedback, future data model, monetization
Roadmap work should follow stabilization unless explicitly chosen.
Ask an agent: Summarize which roadmap items are deferred and why.
Avoid: Building future-scope features ahead of urgent fixes.
Agent Context
Evidence belongs below the scan
Useful for agents and audits; secondary for the office PM.
What exists
- A React/Vite app branded publicly as Sleeping Bunnies.
- A quick Add Sleep flow for nap and night logs.
- Today is now the default landing surface and quick-tracking doorway. Live
- Missing child/profile/age data no longer opens a full-page setup gate on
What is not proven
- There is no lint script in package.json.
- Android build/release workflow was not validated during this pass.
- Cloudflare Pages manual deploy was verified on 2026-05-16 with a
- /api/feedback returns log-only received responses unless FEEDBACK_KV is
Source packet
- Generated 2026-06-03 from the active Markdown packet.
- Markdown remains the source of truth; this dashboard adds no execution authority.
Source Health
Files behind this dashboard
- Missing active docs
- 0
- Needs review
- 6
- Old but quiet
- 0
Freshness check
- Needs review: docs/current-state.md (2026-05-16)
- Needs review: docs/next-steps.md (no review date)
- Needs review: docs/product-plan.md (no review date)
- Needs review: docs/design-direction.md (2026-05-22)
- Needs review: docs/architecture.md (no review date)
- Needs review: docs/session-brief.md (2026-05-22)
Repo overview, commands, and documentation entry point.
FoundWhat exists now, what works, what is incomplete, and stale signals.
Needs review - reviewed 2026-05-16Recently completed work, recommended next moves, and work to avoid.
Needs review - no review dateProduct north star, current product shape, and roadmap posture.
Needs review - no review dateExperience principles, visual direction, and interface guardrails.
Needs review - reviewed 2026-05-22Stack, app structure, data model, boundaries, and technical assumptions.
Needs review - no review dateValidation commands, QA expectations, and evidence requirements.
Found - reviewed 2026-06-01Compact restart context, immediate next move, caveats, and reminders.
Needs review - reviewed 2026-05-22