1. Recommended baseline
- Require acceptance criteria.
- Require expected behavior.
- Require scope boundaries.
- Require a test plan or QA notes.
- Require component or service context for engineering-owned work.
- Require rollout and rollback notes for risky changes.
2. Risk categories
Teams should pay special attention to issues involving authentication, permissions, payments, billing, migrations, sensitive data, external APIs, or broad refactors. These areas often need stronger acceptance criteria, explicit test plans, and rollback guidance.
3. Generated output behavior
- Jira comment writing should remain approval-gated.
- Clarification subtasks should be disabled by default and limited to conservative, actionable questions.
- Generated comments should include the review disclaimer.
- Teams should review the work order before using it as an implementation prompt.
4. Prompt profiles
Prompt profiles adjust the generated work order style. Planned profiles include default, strict engineering, AI coding agent, QA-heavy, and regulated/compliance-heavy. Advanced profiles are intended for Advanced edition workflows.
5. Ownership
Project settings are stored in the ProcessLayer backend as the source of truth. Forge storage may cache settings briefly, but it is not the primary system of record.