Skip to content

Document the staged agent implementation playbook #130

Description

@knzeng-e

Prepare a reusable implementation playbook for Dotify, with Product DevNet as a first-class destination alongside mobile/desktop web.

Scope: 20 agent-ready execution recipes with recommended short-lived branch names, dependencies, source files, acceptance criteria, explicit non-goals, evidence handoffs, and a pilot gate. Keep prompts together on dev and create implementation branches when work starts. Include later immersive 3D discovery, sound-reactive presence, CASH/personhood feasibility, privacy-preserving nearby discovery, and evidence-led community expansion.

Local scope: docs/backlog/implementation/README.md.

Acceptance: prompts are actionable without private chat context; dependency graph and relative links validate; existing backlog issues are reused; public roadmap and product-memory entry points are aligned; no application behavior or deployment changes in this task.

Metadata: Priority P1; Track Product SDK; Phase Now; Type Work; Backlog doc docs/backlog/implementation/README.md. Project 5 association is required by repository guidance but the current GitHub connector does not expose Project mutations; leave this explicitly pending rather than claiming synchronization.

Related implementation epics/issues: #85, #87, #88, #89, #90, #12, #13. This documentation task does not complete those features.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

dotify-backlogTracked by docs/backlog/backlog.json and Project 5

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions