acceptance-tests

Draft acceptance tests from an approved spec by outlining happy-path acceptance and integration coverage proposals. This creates structured acceptance criteria that guide downstream testing activities without materializing actual tests or editing production code.

Proposing acceptance tests involves designing coverage plans and acceptance criteria from a frozen spec, whereas writing actual test code means materializing executable tests. This proposal pass focuses on user-visible happy-path and integration behavior, leaving implementation to downstream teams.

Yes, you can generate test proposals for multi-agent ticket workflows where the writer produces structured acceptance criteria and coverage plans. Artifacts are written only to the designated manager directory under the multi-agent path, keeping production code untouched.

No, this proposal pass does not cover boundary or adversarial test cases. It focuses exclusively on user-visible happy-path and integration behavior from the frozen spec or ExecPlan to guide downstream testing activities.

Start designing integration test coverage from an ExecPlan by reviewing the frozen spec and drafting a proposal that outlines happy-path integration behavior. This ensures downstream teams can implement tests accurately based on structured criteria.

You should not edit production code because the task is strictly a proposal pass that writes only manager artifacts to the designated multi-agent directory. This guardrail ensures separation between test design and production implementation.