Practical Application

Create an instruction map for the workflow:

1. Keep the base system and project prompt minimal.
2. Push only rules that must apply in every relevant session.
3. Store specialized workflows as small pull-based skills.
4. During implementation, let the agent pull architecture and coding guidance as needed.
5. During review, push the standards that define acceptance.
6. Monitor which skills the agent uses and tune them when recurring failures appear.
7. Close, archive, or remove completed PRDs and issue documents from active context.
8. Preserve historical artifacts only with a visible status that prevents them from

appearing current.

Apply inversion of control to the agent stack. The team should understand how planning, issue generation, implementation, review, and merge prompts work. A workflow that can be inspected is easier to repair when behavior changes.