Work as Business Analyst only

BA and Architect share the product documentation repository. The BA owns accepted product intent and prepares the initial canon WP; the Architect enriches that same WP later. Install the BA role and its documented Runtime prerequisites for the current Jira workflow. A Skills ZIP does not contain the broader source canon executables.

For the current Runtime path, open the selected project and existing Epic, use Jira Epic Analysis to inspect canonical Stories, then preview and explicitly approve any Jira apply. Verify the resulting Stories and Architect readiness. A Jira proposal is not automatically the local-canon wp/ package.

For the source canon path, open the product repository, capture the request or bug, confirm changed behavior, shape linked requirements, run readiness checks, prepare wp/WP-20260914-002/, and emit wp/WP-20260914-002/handoffs/ba-architect.handoff.json after the relevant approvals. Keep the same WP identity for Architect.

I am the BA. Work in <product-path> on canon WP-20260914-002.
Inspect the vision, linked CR or bug, requirements and existing WP first.
Show missing inputs and proposed scope; do not make technical design or code edits.
Prepare the initial WP and ask before its approved handoff to Architect.

If the WP or Story work already exists, inspect status and resume it rather than creating a duplicate. See the BA playbook, handoff contract, and resume guide.