ticket-analysislisted

Use when starting work on a ticket, before any implementation, or when unsure whether a ticket is ready to implement at all. Turns the business request into an architectural one: a table with a row per acceptance criterion carrying the owning bounded context and layer, the principle that governs it, the guide implementation must load, and the named files — then a walk of the compliance checklist listing what the change puts at risk, so a deviation is decided and recorded here rather than discovered mid-diff. Reads the ticket against the architecture rather than against the existing code, runs a read-only exploratory round, separates blocking questions from assumptions worth documenting, and tests the four conditions that gate entry into implementation. Refuses to proceed if the standards are not actually readable in the session.
konradcinkusz/architecture-standards · ★ 0 · Code & Development · score 72

Install: claude install-skill konradcinkusz/architecture-standards

# Ticket analysis The phase before implementation. Its job is to decide one thing: **is there enough information to implement this ticket without guessing?** It produces an analysis, a list of open questions, and an answer to that question. It writes no production code. **The ticket arrives in the conversation** — pasted, in its own words, with its acceptance criteria. This phase takes no argument and fetches nothing. The gate matters more than the document. A ticket that enters implementation with an unresolved ambiguity does not fail loudly — it produces a plausible diff that solves the wrong problem, and the cost lands in review or in production rather than here. First of three phases: this, then [`IMPLEMENTATION-PHASE.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/delivery/IMPLEMENTATION-PHASE.md), then [`PR-REVIEW.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/delivery/PR-REVIEW.md). [`WORKFLOW.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/delivery/WORKFLOW.md) is how they fit together and how to install them. **Contents** 0. [The standards have to be in front of you](#0-the-standards-have-to-be-in-front-of-you) 1. [Read the ticket against the architecture](#1-read-the-ticket) 2. [The analysis is a table, not prose](#2-the-analysis-is-a-table) 3. [What the change puts at risk](#3-what-the-change-puts-at-risk) 4. [The exploratory round](#4-the-exploratory-round) 5. [Questions and