10c-dev

The closing reflection after a change lands: work out what the change just made pointless — superseded implementations, orphaned helpers, features whose reason to exist disappeared — remove the obvious ones and propose the rest. Runs automatically at the end of any non-trivial coding task, and on request: "what can we delete now", "tidy up after this", "what is redundant now", "remove the old one", "posprzątaj", "co jest teraz zbędne", "usuń stare".

Review a diff, branch, or PR against correctness, security, breaking-change, and quality standards — runs the validation gate, applies the built-in checklist plus any repo-local one, and produces severity-ranked findings with an approve/request-changes verdict. The review engine behind the self-review step of the build cycle.

Use for ANY request to write, change, prototype, refactor or debug code — a new app, a new feature, a bug fix, a spike, "try something", "add a feature", "fix this", "let's try", "build me an app", "refactor this", "dodaj funkcję", "popraw", "spróbujmy", "zrób aplikację", "zrefaktoruj". Interviews the human before building, picks the right rung of the prototype→production ladder, builds the minimum that works, then reflects on what the change made obsolete. Do NOT skip it because the task looks small.

Drives the full build cycle for a task. Moves the tracker ticket to In Progress (for a real key), runs the `coding` skill's phases (rung, interview, spec, minimal build, tests at R2+, proof on the live app, self-review with `code-review`), offers an adversarial critic, closes with `cleanup` and a project-model update, then offers to commit and push; the ticket status follows the code (In Progress locally, In Review once on the shared branch, Done once checked in production). Accepts a real ticket key of ANY project (e.g. `ABC-123`, `PROJ-42`), or a synthetic local key (e.g. `LOCAL-20260729-1430`) for ad-hoc work with no ticket.

Read, manipulate and administer Jira Cloud tickets from a session. Search with JQL across every accessible project, get full issue detail with comments and available transitions, create, comment, transition, assign, browse boards (kanban and scrum auto-detected), list projects, and reach anything else through a raw REST escape hatch. Per-user API token stored outside the repo, with a first-run setup walkthrough. Use for "/jira", "find a jira ticket", "create a ticket for", "what's assigned to me in jira", "comment on ABC-123", "move ABC-123 to in progress", "assign ABC-123 to someone", "search jira for", "JQL", "board overview", or any reference to a Jira issue key or a *.atlassian.net link.

Build and maintain a high-level map of what a project is FOR — which problem each part solves, what is load-bearing, what is nice-to-have, what is legacy kept alive for one reason, what is already dead. Use when starting work on an unfamiliar repo, when asked to "explore this codebase", "map this project", "what does this project even do", "poznaj projekt", "zbuduj mapę projektu", and to update the map after a feature lands or a capability is retired. Built by reading the code AND interviewing the human — not by reading the code alone.

One-time setup for the 10c-dev workflow — checks runtimes, connects and authenticates the ticket tracker and Slack, installs the browser automation, then interviews you to write this repo's .claude/task-flow.json and verifies every piece works.

Read and write Slack from a session through the `agent-slack` CLI, which acts as the user's own Slack account. Covers reading channels, DMs and threads, posting and editing messages, creating channels and inviting people, setting a channel topic, and a raw Web API escape hatch for anything the CLI lacks. Use whenever a task touches Slack: "read this thread", "post to #channel", "create a channel", "who is in this channel", "set the topic", "search Slack", or when a `*.slack.com` link or a `C…`/`D…`/`G…` id shows up. Not installed yet, or `auth test` failing? Read SETUP.md first — it is a one-time setup you can run yourself.