Du kannst nicht mehr als 25 Themen auswählen
Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
893B
893B
Skill: Spec Interview
Purpose: Elicit clear, unambiguous requirements before drafting a technical spec.
Steps
- Ask what problem is being solved and for whom.
- Identify the affected stack(s) (ASP Classic, VB6, C#, PHP, and which database engine).
- Clarify inputs, outputs, and edge cases (invalid input, empty data, concurrency).
- Confirm acceptance criteria in Given/When/Then format.
- Identify files/modules likely affected.
- Confirm rollback or backward-compatibility needs if database schema changes are involved.
- If
.devfoundry/references/environments.mddoes not yet list a Build/Test/Lint command for the affected stack, ask the user for the exact command(s) and record them there before drafting the spec — QA Verifier and Builder both depend on these being known, not guessed. - Summarize findings back to the user for confirmation before drafting the spec.