Browse Specs & Powers

Guides agents to write pragmatic, business-logic-focused tests that match existing project patterns and avoid brittle or low-value coverage.

Guidance for adapting to project-specific conventions and constraints: match existing code style and architecture, treat rules files as binding, and follow established patterns instead of defaults.

Guidance for delivering changes in small, validated increments: break large requests into manageable steps, verify each chunk before continuing, and avoid building on unverified code.

Practical guidance for how the agent should work day‑to‑day: how to use third‑party packages safely, how to plan tasks and get approval, and how to keep implementations simple and correct.

How I like to write Jira tickets

Test spec for Phase 3 manual testing