← ClaudeAtlas

codex-astra-implement-with-tddlisted

Implement an Astragentic full ticket one acceptance criterion at a time with measured red/green behavior and bounded write ownership.
thientranhung/astragentic · ★ 4 · AI & Automation · score 70
Install: claude install-skill thientranhung/astragentic
# Criterion to red to green Load the dispatch brief, exact base, ticket criteria, write-set, validation commands and project guidance. Confirm the current worktree/branch. Clarify contradictory criteria; do not choose product behavior yourself. Quick tickets use their smaller loop instead of manufacturing TDD evidence. For each testable criterion: choose an observable seam, write the smallest meaningful failing behavior test, run it and record the expected assertion failure, implement, then run green. An import/setup error is not evidence of missing behavior. Avoid batching a speculative test suite ahead of learning from the first real failure. Mock only actual system boundaries such as external services/time/randomness. A source-string assertion or a mock-call count alone does not prove the user behavior. Do not weaken assertions, skip tests or alter fixtures merely to make green. To check a red against the tree without your change, never use a bare `git stash pop` or `drop`: the stash stack is shared by every worktree and the top entry may be another Builder's. `git stash push -u -m "red <ticket>"`, read your entry's SHA (`git stash list --format='%H %gs'`), `git stash apply <sha>`, then drop the `stash@{n}` that SHA sits at now (`git stash list --format='%gd %H'`); `git stash drop <sha>` is refused. When deleting or replacing tests, record each removed behavior, its requirement, whether production still supports it, and the replacement test or explicit retirement reaso