TC FE Prep (discovery stub)

Thin entry for agent skill discovery. Full procedure: WORKFLOW.md.

When invoked:

1. Announce once: Using **tc-fe-prep-workflow** to prepare FE manual test cases.
2. Read and follow WORKFLOW.md end-to-end — every step, gate, and reference.

Claude Code shortcut: /tc-fe-prep → commands/tc-fe-prep.md.

Contents

Every must-read file for this workflow, linked directly from here. References already linked above are not repeated.

Every run

Read these on every run — each one is used in every TC prep session.

• WORKFLOW.md — always: the full procedure, read end to end.
• must-never.md — read at the start of every run, before Step 0, and again before any write or post — the skill-specific MUST / NEVER table; every row binds drafting, review and publishing.
• requirement-gates.md — before Step 3 — read and follow Steps 2a, 2.5 and 2.6, end to end.
• design-and-review.md — before Step 5 — read and follow Steps 3, 4 and 4.5, end to end.
• shared-preamble.md — at the start of every run, before the first reply (preamble, constraints, tone).
• tc-quality-standards.md — while writing every TC row.
• workspace-guide-discovery.md — read on the first response, to locate the workspace project guide for this workflow.
• helix-session-constraints.md — read once at session start.
• user-communication.md — read before any message to the user.

At the step or trigger stated next to each file

Read each file below at the point written next to it, not up front. If that step or trigger does not happen in this run, the file is not read.

• csv-export-rules.md — read when exporting the CSV file(s).
• jira-comment-adf-template.md — before building the Jira comment ADF, and always on a "draft only / do not post" request — write the .adf.json + preview per this template.
• jira-comment-post-review.md — right after posting a Jira comment — full review checklist.
• jira-fast-publish.md — read when the fast-publish step returns an error.
• jira-linebreak-conversion.md — before posting a table that contains line breaks to Jira.
• publish-options.md (shared) — read when Step 7 has no browser tool or no signed-in Jira session — Option C manual handoff, comment Not posted.
• jira-wiki-vs-markdown.md — read when that manual handoff is prepared — which comment format to hand over.
• qa-closing-shared.md — before reporting done — shared QA closing gates, including the cross-ticket conflict check.
• session-closing.md — after the verify gate passes — artifact index, next workflow, handoff.
• shared-must-never.md — before any write or post — rules shared by every workflow.
• agent-rationalizations.md — read when tempted to skip a step; each excuse has its correct action.
• coverage-delta-template.md — read after the coverage review, before the full draft.
• csv-template-types.md — read before exporting a CSV.
• figma-design-comparison.md — read before judging any UI or visual result against the design.
• long-workflow-todos.md — read when the workflow has many steps; keep the todo list.
• portable-content.md — read before writing any repo, path, ticket number or project value into the skill output; nothing project-specific is hardcoded.
• proactive-qa-triggers.md — read when a QA follow-up could be suggested, at any point in the run (including session close).
• qa-evidence-gates.md — read before any completion claim.
• round-time-contract.md — read when a round starts and before reporting times.
• skill-invocation-discipline.md — read before invoking or switching skills.
• skill-routing.md — read when choosing which skill handles a request.
• skill-rules-style.md — read before asking the user or stopping on a missing input.
• test-md-format.md — read when exporting Test.md.
• ac-ec-coverage-review.md — read before drafting; AC / EC coverage review.
• jira-formatting.md — read before posting the Jira comment.
• prerequisites.md — read before step 1.
• publish-options.md — read when choosing how to publish.
• qase-import-format.md — read before exporting the Qase CSV.
• worked-example.md — read only when you need a format reference for the TC table or comment (a full anonymized worked example).

Only when the stated trigger occurs (outside manual TC drafting)

This workflow drafts test cases and never executes them or records verdicts. Read each file below only when its trigger actually happens in this run (for example the user asks to run a case, or a tool error needs a cause); it is not part of the every-run reading.

• bug-priority-matrix.md — read before setting any priority or a PWMI / FAILED verdict.
• customer-escape-prevention.md — read before any QA run; the gates that stop shipped defects.
• defect-report-completeness.md — read before writing up any defect or non-pass.
• non-pass-challenge-gate.md — read before recording any result that is not PASSED.
• playwright-preflight.md — read before any Playwright run.
• qa-debug-discipline.md — read when a test is flaky or a tool errors.
• resilient-selectors.md — read when writing or fixing Playwright selectors.
• result-quality-gate.md — read before any verdict leaves the round.
• root-cause-investigation.md — read before naming a cause for any failure.
• test-through-real-steps.md — read before testing an action; no API shortcut for the action under test.

Refusal-first (precondition gate)

All preconditions and refusal rules are in WORKFLOW.md. MUST NOT start until the user provides a Jira story key or URL and required config is resolved.

QA closing (mandatory before "done")

All close-out gates are in WORKFLOW.md, verify-closing-checklist.md (TC FE section), and tc-final-review-report.md. MUST NOT report done until they pass.

Dependencies

Run the check for each of these before step 1 — check commands and install hints are in dependencies.md:

• curl
• Python 3 + openpyxl (xlsx only)
• Atlassian MCP
• Jira REST credentials (ADF-direct publish)
• Qase
• a browser for the HTML preview
• superpowers:systematic-debugging