agentdesk

AgentDesk

Outcome

Turn a software repository into a controlled multi-session development system:

Versioned task cards, PM-owned canonical state, real independently visible role tasks, role-bound execution, proactive callbacks, immutable Git evidence, explicit acceptance, and recoverable handoff.

The observable loop is non-negotiable:

PM/Leader task
→ verified independent role task named `role_no . role_name`
→ real dispatch delivery
→ dedicated worktree execution and durable report
→ worker proactively messages the PM/Leader source task
→ PM independently accepts and integrates
→ dependencies unlock
→ heartbeat reconciles only if the primary callback path fails

Repository records make this loop recoverable; they do not substitute for creating, addressing, or messaging the real tasks.

When a question needs competing viewpoints before execution, AgentDesk can prepend a bounded consultation loop: one Leader opens one to three read-only consultation tasks, collects independent first-round callbacks, optionally runs one cross-check round, synthesizes disagreements, and asks the Owner to confirm what—if anything—becomes a decision or task card. Consultation is advisory and never substitutes for the execution loop above.

Automate coordination, not authority. Keep product decisions, risky approvals, merging, and release behind their declared gates.

Resolve The Requested Mode

Choose the primary mode from the request and repository state. Consultation may precede PM, but its output does not silently enter execution:

1. Initialize — scaffold or upgrade a project workflow.
2. Consultation — open zero to three bounded, read-only advisory tasks around one topic, collect their callbacks, synthesize, and request Owner confirmation.
3. PM — clarify requirements, configure roles, create and dispatch cards, review deliveries, update state, and unlock dependencies.
4. Worker — implement one assigned card inside its scope and produce a delivery report.
5. QA / Integration — test a frozen candidate or combine accepted commits under a dedicated card.
6. Validate — check project structure and state without changing business code.
7. Recover — reconcile conflicting state, lost callbacks, stale revisions, expired leases, or invisible Git evidence.