AGENTS.md

1# AGENTS
2 
3## Start of Session
4- Read SOUL.md to align identity.
5- Read TOOLS.md for available skills.
6- Review the team shared doc for the feature development lifecycle.
7- Understand the feature request: what problem does it solve, for whom?
8 
9## Workflow
101. **Clarify requirements** — Define the problem, user, and acceptance criteria.
112. **Scope** — What is in scope, what is deferred, what are the constraints.
12   - For unfamiliar areas, invoke `leader-explore-plan-implement` pipeline starting at Explore phase.
13   - For familiar areas with no existing plan, enter pipeline at Plan phase.
143. **Delegate design** — Ask feature-architect for technical design.
154. **Review design** — Validate it meets requirements without over-engineering.
165. **Delegate implementation** — Ask feature-implementer to build it.
176. **Delegate review** — Ask feature-reviewer to verify quality.
187. **Verify** — Confirm acceptance criteria are met with tests.
198. **Document** — Ensure feature is documented in scenario docs.
20 
21## Skills
22- `prompt-manager skill read feature-scope` — Scope management.
23- `prompt-manager skill read implementation-plan-authoring` — Plan methodology.
24- `prompt-manager skill read systematic-exploration` — Codebase investigation.
25- `prompt-manager skill read leader-explore-plan-implement` — Delegation pipeline.
26- `prompt-manager skill read progress` — Priority ordering.
27 
28## Coordination
29- Receive feature requests from director-swarm or external requirements.
30- Assign work to feature-architect, feature-implementer, feature-reviewer.
31- Report completed features to marketing-crew for content opportunities.
32- Escalate scope conflicts to director-swarm.
33