PulsePlate Workflow

When to use

• •Starting any new task in this repository.
• •Clarifying scope before coding, testing, or documentation changes.
• •Ensuring coordinator-first routing and AGENTS policy compliance.

Inputs required

• •Task goal in one sentence.
• •Candidate paths to change (or unknown).
• •Expected output (code change, docs update, report, or review).

Procedure (commands)

1. •

   Baseline repo state:

   bash

   git status --short
   git log -1 --oneline
   

2. •

   Load policy context:

   bash

   ls AGENTS.md RUNBOOK_AGENT.md
   find . -name AGENTS.md -maxdepth 4 | sort
   

3. •

   Identify relevant module scope:

   bash

   rg -n "Scope and layout|This AGENTS.md applies to" app/AGENTS.md core/AGENTS.md frontend/AGENTS.md ios/AGENTS.md tests/AGENTS.md
   

4. •

   Start coordinator-first routing for multi-agent work:

   • •Use .cursor/agents/agent-coordinator.md as entrypoint.

Output format

• •Task summary: one paragraph.
• •Scope: exact files/directories in scope.
• •Policy checks: list of AGENTS/RUNBOOK files used.
• •Execution plan: ordered steps with command list.
• •Risks: concrete constraints and fallback path.

If blocked, always include:

• •Raw failing lines.
• •file:line:error pointers.
• •Minimal next-fix steps.

Guardrails

• •Do not claim green/ready/mergeable without local gate evidence.
• •Avoid bypassing hard rules in AGENTS.md.
• •Refrain from editing unrelated dirty files.
• •Do not use GUI/RPA automation in this workflow.

SoT links

• •AGENTS.md
• •RUNBOOK_AGENT.md
• •.cursor/agents/AGENTS.md
• •.cursor/agents/agent-coordinator.md
• •app/AGENTS.md
• •core/AGENTS.md
• •frontend/AGENTS.md
• •ios/AGENTS.md
• •tests/AGENTS.md