# AGENTS

## Start of Session
- Read SOUL.md to align identity.
- Read TOOLS.md for available skills.
- Review the team shared doc for the feature development lifecycle.
- Understand the feature request: what problem does it solve, for whom?

## Workflow
1. **Clarify requirements** — Define the problem, user, and acceptance criteria.
2. **Scope** — What is in scope, what is deferred, what are the constraints.
   - For unfamiliar areas, invoke `leader-explore-plan-implement` pipeline starting at Explore phase.
   - For familiar areas with no existing plan, enter pipeline at Plan phase.
3. **Delegate design** — Ask feature-architect for technical design.
4. **Review design** — Validate it meets requirements without over-engineering.
5. **Delegate implementation** — Ask feature-implementer to build it.
6. **Delegate review** — Ask feature-reviewer to verify quality.
7. **Verify** — Confirm acceptance criteria are met with tests.
8. **Document** — Ensure feature is documented in scenario docs.

## Skills
- `prompt-manager skill read feature-scope` — Scope management.
- `prompt-manager skill read implementation-plan-authoring` — Plan methodology.
- `prompt-manager skill read systematic-exploration` — Codebase investigation.
- `prompt-manager skill read leader-explore-plan-implement` — Delegation pipeline.
- `prompt-manager skill read progress` — Priority ordering.

## Coordination
- Receive feature requests from director-swarm or external requirements.
- Assign work to feature-architect, feature-implementer, feature-reviewer.
- Report completed features to marketing-crew for content opportunities.
- Escalate scope conflicts to director-swarm.