[ANDROAPP-7640] Add test-flow-architect agent and supporting skills

[rohit-wa]

Summary

Adds the test-flow-architect Claude Code agent plus three new skills under .claude/, and extends the existing android-testing skill with per-component test-tag pattern documentation.

The agent automates the QA workflow: reads Zephyr test cases via the Atlassian MCP, surveys existing flows on Confluence, decides whether new cases extend an existing flow or need a new one, claims a dedicated DHIS2 program on the testing server (per-flow), drafts a flow-plan.md for review, and — only after explicit user approval — hands off to the android-testing skill to generate Kotlin Robot/Test files.

Jira: ANDROAPP-7640

Files

New (4):

• .claude/agents/test-flow-architect.md — the agent prompt and workflow
• .claude/skills/test-flow-planner/SKILL.md — flow-grouping heuristics + flow-plan.md schema + program-reservation procedure
• .claude/skills/zephyr-test-fetcher/SKILL.md — Atlassian-MCP-based Zephyr fetcher (read-only)
• .claude/skills/confluence-workflow-reader/SKILL.md — Confluence reader for existing flow precedents

Updated (1):

• .claude/skills/android-testing/SKILL.md — document the INPUT_<COMPONENT_NAME>_FIELD testTag convention and link to the design-system docs/source so test authors can locate tags for non-text inputs.

Key behaviours enforced

• Always ask the user which DHIS2 testing instance to target — the slug rotates per cycle; never reuse a base URL from a prior session.
• Plan mode is read-only against Zephyr, Confluence, and the testing server. No code is written and no server mutations happen until the user approves the plan.
• Confluence writes require explicit "approved, publish" from the user.
• Default is one program per flow. Sharing allowed only when new cases extend an existing flow's workflow.
• Never modify Antenatal Care or Information Campaign programs — they are used by legacy tests.
• Read-only on Zephyr / Jira test cases — the agent never transitions, edits, or comments on ANDROAPP Test issues.

How to invoke

@test-flow-architect Plan automation for ANDROAPP-1234, ANDROAPP-1456.

In plan mode the agent will: ask which DHIS2 instance to target, fetch the Zephyr cases, check existing flow plans on Confluence, grep the repo for reusable Robots, and produce a flow-plan.md ending with Approve to implement?.

Test plan

• Trigger plan mode with a small Zephyr case set in a fresh clone and confirm the agent prompts for the testing-instance URL.
• Confirm the agent surfaces the per-flow program reservations and stops at Approve to implement? without writing Kotlin or mutating the server.
• After approval, confirm the agent claims the program(s) on the user-specified instance and generates Robot + Test code via the android-testing skill.
• Verify the updated android-testing SKILL.md guidance helps locate the correct testTag for at least one non-text design-system input (e.g. checkbox or dropdown).

🤖 Generated with Claude Code