implement-issue

Implement issue

Resolve the issue end to end against the current repository, or establish with evidence that no implementation is needed.

Gates

• Read the issue, project instructions, vision, contribution guidance, Definition of Ready, Definition of Done, relevant domain skills, real project commands, affected code paths, tests, and reproduction before deciding.
• Always perform and record web search for current evidence before presenting options. Prefer official and primary sources, reconcile them with the versions in the checkout, and treat remembered links only as search leads. Stop if the search cannot produce current evidence relevant to the decision.
• When grill-with-docs or grill-me is registered, run its actual user-question loop before presenting options. Prefer grill-with-docs; if neither exists, note that once and continue.
• Before proposing an option, assemble one neutral evidence packet from the issue, repository, reproduction, project contracts, current web research, and shared current-state artifacts. Derive every option from this same packet.
• Define one comparison rubric from the issue outcome, constraints, and acceptance criteria before scoring. Give every viable option equivalent decision-relevant validation:
  • for UI/UX differences, show each materially different experience;
  • for architecture or workflow differences, show each relevant flow;
  • for interaction-heavy or technical claims, use comparable short-lived prototypes or measurements when static evidence cannot decide them. Equivalent checks do not require equal implementation effort. Label observed facts, proposed behavior, and prototype-only shortcuts.
• If an option reveals an evidence gap, run the same relevant check for every affected option. When that is impossible, disclose the unequal evidence and reduce confidence before comparison.
• Keep prototypes local and disposable, retain only reviewable captures and findings, and remove them when the grill concludes. Do not deploy or publish them. Preserve or promote a prototype only with explicit user approval; keep approved prototype material outside the selected worktree until its git-workflow synchronization gate passes.
• Compare two to four genuinely distinct viable options against the declared rubric, then recommend one and wait for the user's choice unless automatic mode applies. Include a compact evidence digest with the most relevant source links, checked project versions, scores, and remaining uncertainty.
• When current evidence conclusively fails a required prototype or readiness threshold, report that stop without asking whether to bypass the gate.
• For any code or test change, complete the project gate, one bounded /code-review fix-all, and /create-pr.