Claude Skills by bturksoy

Produces an Architecture Decision Record (ADR). Permanently records a technical decision, the alternatives considered, the consequences, and the implementation guidance. The instructions the developer sees inside a story are produced here.

Produces or updates the OpenAPI contract. Endpoints, schemas, error format, pagination and authorization are defined in one place. Frontend and backend consume this contract and cannot change it.

Determines the system architecture and technology stack. The Solution Architect designs, the CTO approves. Produces component boundaries, data flow, NFR mechanisms and initial ADRs. Operates the CTO-STACK and ARCH-DESIGN gates.

Routes a story to the right agent. Runs a readiness check, detects missing context and completes the story if needed. A preparation step before /dev-task.

Creates a bug record and triages it — priority, owner, root-cause hypothesis and regression test plan. Without arguments, prioritizes the open bugs.

Produces a change log entry from completed stories and bug fixes. Written in the user's language using Keep a Changelog + SemVer format.

Performs an independent code review. Produces findings across correctness, security, scope fidelity, rule compliance, readability and test quality. Operates the CR-CODE gate.

Compacts bloated documents, refreshes index files, checks whether content copied into stories is still in sync with its source, and removes duplication. Provides a direct token saving.

Designs the data model — ER diagram, table schema, constraints, indexes and migration plan. Treats the data dictionary as the canonical source. Produces db/schema.sql and docs/data/ER.md.

Produces the design token set and component catalogue. Derives the component list from the UX screens and writes variant, state, prop and accessibility specifications for each.

Implements a single story end to end. Runs a readiness check, invokes the right developer agent, runs the tests, obtains a code review and updates the story. The main development loop.

Runs the Product Owner and Business Analyst in parallel to flesh out the project. Looks through two different lenses, separates agreement from contradiction, and presents contradictions to the user as decisions. A mandatory step before the PRD.

Audits a story, sprint or release against the Definition of Done using evidence. The gate where "done" is decided. Operates the QA-DONE gate.

Splits the phase's requirements into epics. Each epic carries a capability group, its requirements, the architectural layer and its dependencies. One level above the story breakdown.

Produces effort estimates for an epic or story list. States the uncertainty band, the assumptions, and the factors that inflate the estimate.

Produces a work handoff packet from one agent to another. Conveys what was done, what remains, the decisions made and the pitfalls, in no more than 200 words. Used at session end or on a role change.

Shows the App Studio command list grouped by phase. With an argument, explains what that command does.

Resolves an urgent production issue on a fast path — impact analysis, root cause, minimal fix, regression test and expedited release. Skips the normal sprint flow but not the quality bar.

Starts a new project. Takes the project idea, works with the CEO to define business goals and success metrics, selects the agent roster and review mode based on project scale, and sets up the directory structure and state files.

Brings an existing codebase into the App Studio system. Analyses the code and produces CONTEXT.md, a draft architecture, a technical debt list and reverse-engineered requirements. The entry point for brownfield projects.

Verifies the performance budgets. Runs load tests, compares measurements against targets, analyses bottlenecks and detects regressions. Operates the PERF-BUDGET gate.

Produces the Product Requirements Document (PRD). Turns the discovery output into a structured, prioritized and measurable product definition. Operates the PO-SCOPE gate.

Runs the tests, reports the results, analyses failures and turns genuine defects into BUG records. Writes missing tests when coverage gaps are found.

Prepares the release plan, gathers all quality gates, validates the migration and rollback plan, and obtains the CEO go/no-go decision. Operates the OPS-READY and CEO-GONOGO gates.

Turns PRD capabilities into testable functional requirements (REQ), measurable non-functional requirements (NFR) and a data dictionary. Operates the BA-REQ and QA-TESTABLE gates.

Runs a sprint or release retrospective. Produces what went well, what did not, root causes and owned action items. Where process improvement happens.

Splits the project into phases that each deliver value independently, assigns scope and exit criteria to each, and produces the release plan. The phasing step — decides which requirement ships in which release.

Runs several roles in parallel on any topic, gathers analysis through different lenses, separates agreement from disagreement, and presents the decision to the user. A general-purpose discussion tool for hard, cross-disciplinary decisions.

Detects scope creep. Compares the current backlog against the original goals, finds work not tied to a goal, and produces cut recommendations.

Performs a security review of code and configuration. Checks OWASP items, authorization logic, secret leakage, and whether the threat model's mitigations were implemented. Operates the SEC-REVIEW gate.

Sets the sprint goal, assigns stories to agents, orders dependencies, sets up parallel work lanes and flags risks. Where task assignment happens. Operates the DM-PLAN gate.

Detects the project state and tells you where to continue. Bootstraps a new project or finds the missing step in an existing one. The first command of every session.

Produces the project status dashboard — phase, sprint, progress, blocked work, open gates, risks and a token-usage note. Then suggests a single next step.

Breaks an epic into stories. Each story is written as a self-sufficient TASK PACKET so the developer agent can implement it without opening any other file. Story types and test scenarios are assigned by the QA Lead. The heart of token optimization.

Delivers a feature (epic) end to end with the whole team — contract, data, service, interface, tests, review. Runs agents in the right order and in parallel where possible. Vertical slice delivery.

Produces the test strategy and a release-scoped test plan. Sets risk-based coverage, defines the test pyramid, and decides how much of each area gets tested.

Produces a STRIDE-based security threat model. Identifies assets, trust boundaries and threats, and assigns a mitigation and verification method to each. Operates the SEC-THREAT gate.

Produces user flows, information architecture and wireframe specifications. Translates requirements into the language of screens and interactions. Operates the UX-FLOW gate.