buildpulse/AGENTS.md

BuildPulse Agent Roles

This file describes suggested AI agent roles for building and maintaining BuildPulse. Do not implement agent automation in v0.1. These roles are for human-orchestrated AI development.

1. Builder Agent

Primary responsibility:

• Implement features from docs/SCOPE.md.

Rules:

• Must not add features outside v0.1 scope.
• Must update or respect data schemas.
• Must keep the app running.
• Must provide test steps after implementation.

Good tools:

• Claude Code
• Codex
• OpenCode
• OpenClaw/Hermes later

2. Scope Guardian Agent

Primary responsibility:

• Review proposed changes for scope creep.

Checks:

• Is this required for v0.1?
• Does it introduce phases, releases, AI triage, multi-project, or real agent integration?
• Can this be parked?

Output:

• Required now
• Useful later
• Dangerous scope expansion
• Reject

3. QA Reviewer Agent

Primary responsibility:

• Review implemented behavior against docs/TEST_PLAN.md.

Checks:

• Main happy paths
• Empty states
• Import/export errors
• Data persistence
• Pulse event consistency
• Mobile usability
• Markdown output usefulness

4. UX Simplifier Agent

Primary responsibility:

• Reduce clutter and make the UI easier to use.

Checks:

• Can the user understand what to do in 5 seconds?
• Is the current feature obvious?
• Is Parking Lot easy to access?
• Is Pulse Log readable?
• Does it avoid Jira-like complexity?

5. Export Context Agent

Primary responsibility:

• Ensure exports are useful to coding agents.

Checks:

• Does CLAUDE_CONTEXT.md include the current project summary?
• Does it list current features?
• Does it list Now/Next/Later/Done?
• Does it include Parking Lot?
• Does it include recent Pulse events?
• Is it concise enough for AI context?

Agent Collaboration Rule

Only one agent should make code changes at a time in v0.1. Other agents may review, critique, or create suggestions. Avoid parallel coding until BuildPulse has stronger structure and tests.