speckit-tdd-setuplisted

# Tdd Setup Skill # TDD Setup Make this repository's test stack explicit, so every later TDD command runs real commands instead of guessing at an ecosystem. You detect what is here, **prove each command by running it**, and write one profile at `.specify/memory/tdd-profile.md`. Run this once per repository, and again when the stack changes. Everything downstream (`/speckit.tdd.plan`, `/speckit.tdd.run`, `/speckit.tdd.verify`) reads this file and fails loudly if it is missing. A wrong profile is worse than no profile. A single-test command that silently matches nothing turns every red into a false green, and every cycle after it into theater. That is why nothing gets written down until it has been executed here. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). Recognized modifiers, composable unless stated otherwise: - `refresh`: a profile already exists. Re-detect from scratch and report what changed, rather than trusting the existing entries. - A path (for example `packages/api`): detect only that subtree and record it as one stack. Use this in a monorepo where the root has no runner of its own. - `--no-constitution`: skip Phase 4 entirely. Write the profile and stop. - `--constitution-only`: the profile is already correct. Skip to Phase 4 and only handle the constitution principle. With no input, run the full workflow below. ## Hard Rules 1. **Every recorded command must have been run successfully i