bro-give-me-spec

Bro Give Me Spec

Your task is to create a specification of the result: to lock down what и why must change and by which observable conditions the result is ready, without defining the method of implementation. DO NOT WRITE code and DO NOT DRAW UP implementation steps.

GENERAL RULES

MUST follow the dialogue rules!
MUST follow and NOT violate the order of work!
The specification MUST be unambiguous, without variations and open questions. Product ambiguities MUST be resolved with the human.
Acceptance criteria MUST cover the target result with observable statements. Do NOT specify the verification method (automated test, manual check, build, etc.) in the criterion.
The specification does not set the order of writing tests and implementation and does not require TDD.

CONSTRAINTS / STOP

FORBIDDEN to add to the specification steps, stages, executor tasks, the chosen solution architecture, code, diff, patches, pseudocode, and instructions on which files to create or change. Existing paths, types, and methods are permissible in "Task and context" and "Target result" as an anchor of the current state, not as a recipe for editing.
FORBIDDEN to add sections beyond the template structure. The section Принятые решения is permissible only if there are recorded agreements.
FORBIDDEN to invent facts or criteria. Ambiguity of the result, scope, or acceptance MUST be resolved before the specification is ready.
FORBIDDEN write the specification file until the person has named an unambiguous path. The path named in the current request is already considered an answer — do not ask for it again. If the file at the given path already exists — FORBIDDEN to update it without explicit approval to update.
FORBIDDEN when CreatePlan (or an equivalent) is available, to ask for the placement path or write the specification file yourself instead of calling the tool.
FORBIDDEN to propose an implementation plan or /bro-give-me-plan as a continuation of the specification.
When the specification is formed and the review is passed, suggest exactly one next step: /bro-do-it. Do not offer a menu of next steps.

ORDER OF WORK

GATHER from the code and context the information necessary for an unambiguous description of the current state, the target result, the scope, and the checks.
REQUEST the missing information from the person. MANDATORY comply with the dialogue rules. If necessary, prepare closed decision points for the section Принятые решения.
CHECKthat every changed scenario from the target result is covered by an acceptance criterion and that every criterion is observable without describing the method of verification.
DETERMINE which workflow needs to be used, following the workflow determination rules.
CONNECT the file with the instructions of the selected workflow. COMPLY with all instructions from the selected workflow.

WORKFLOW DETERMINATION RULES

Below are the rules for how to determine which workflow to use. DO NOT READ the file with the instructions before selecting the workflow. SELECT the workflow based on the criterion.

create-plan

Use if:

in the current session the tool CreatePlan is available (or an equivalent harness for creating a plan)

When selecting this workflow DO NOT ASK for the placement path.

Instruction file: create-plan

file-spec