mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-22 01:01:12 +00:00
Oleksandr Bezdieniezhnykh
f29897cb3a
User feedback after a transitionJiraIssue call returned a bare
{"success": true} that I trusted blindly: the rule should require
explicit verification and stop-and-ask on any ambiguous response.
Two targeted clarifications:
- .cursor/rules/tracker.mdc - Tracker Availability Gate now lists
the full set of failure modes (non-2xx, timeout, empty body,
opaque success) and bans automatic retries. Adds an explicit
read-back requirement when the response is minimal, and adds
"abort" to the user-choice menu.
- .cursor/skills/implement/SKILL.md - Step 5 (In Progress) and
Step 12 (In Testing) now spell out the STOP-and-ASK rule inline
instead of just pointing at tracker.mdc. Adds the read-back
verification step for opaque responses.
Co-authored-by: Cursor <cursoragent@cursor.com>
17 lines
304 B
Markdown
17 lines
304 B
Markdown
# Autodev State
|
|
|
|
## Current Step
|
|
flow: greenfield
|
|
step: 7
|
|
name: Implement
|
|
status: in_progress
|
|
sub_step:
|
|
phase: 7
|
|
name: batch-loop
|
|
detail: "batch 48 — AZ-508 (ISO timestamp helper consolidation)"
|
|
retry_count: 0
|
|
cycle: 1
|
|
tracker: jira
|
|
last_completed_batch: 47
|
|
last_cumulative_review: batches_43-45
|