trade-imports-journey-config-ui

Test-first bug-fix workflow — write a failing regression test before any code change, fix minimally, then verify. Use when fixing a defect in this codebase.

Extract delivery stories from a design conversation or document. Strip the conversation of noise, Example Map each decision, sequence by dependency and walking skeleton, write feature README and story files using the project template.

Reviews proposed implementation stories as a senior/principal engineer. Use after an initial product/technical discussion has produced one or more draft stories, before implementation begins. Focuses on story slicing, codebase evidence, technical design, sequencing, refactoring, assumptions, and implementation risk.

Editorial review and writing process for documents that humans will read - PR descriptions, READMEs, design docs, commit bodies, RFCs. Recursively drills from surface text to essence by asking what we're trying to say and why; includes a style guide of mechanical rules. Use when the user asks to review, sharpen, edit, or write a doc.

Rigorous agent-driven story implementation workflow — explore, plan, then test-first per module with qa-test-planner, code-reviewer, and refactoring-enforcer gates. Use when implementing a feature/story file from features/.

Reviews implementation stories from a QA/test strategy perspective. Use after stories have been shaped by product and engineering. Focuses on valuable tests, regression risk, testability, acceptance criteria, fixtures, automation, and how tests should be run.

Enforce rigor in technical analysis reports intended for another AI to consume — show raw data before interpretation, define domain terms with contrasting examples, prevent jargon and hallucination. Use when producing data-analysis reports or research summaries with quantitative claims.

Run the full story review cycle — engineering lens (sizing, sequencing, codebase fit) followed by QA lens (test strategy, risk, acceptance criteria). Use after stories have been drafted from a design conversation, before implementation begins.

Select and write high-value unit tests for this Node/Hapi codebase using a QA-first selection process. Single source of truth for test selection rules.