Design -> adversarial review -> breakdown -> implement -> ship pipeline for your AI Code, with Jira sync, an enforced approval gate, a quality gate, budget protection and a live dashboard.
Skills 17 in the Claude listing
breakdown Decompose a hardened SDD into at most 8 atomic, dependency-ordered tasks, create them as Claude Code tasks and (optionally) Jira subtasks, and write task_state.json. checkpoint Show, write, or clear takshak's resume checkpoint, or clear the current plan. dashboard Open the read-only takshak pipeline dashboard (risks, tasks, amendments, budget, patterns, inbox) and call out anything that needs action. design Take a requirement or Jira ticket through a staged, evidence-backed design — discovery interview and design notes, numbered requirements, options recorded as ADRs, a high-level SDD, adversarial harden doctor Diagnose a takshak installation — Python version, framework.json, whether the configured test/lint/typecheck/build commands actually run, Jira config, statusline wiring, and legacy hook wiring. init Set up takshak in the current project in one step — detects the stack, writes .claude/framework.json and state files, wires the budget statusline, seeds CLAUDE.md, optionally commits team settings so lld Derive the low-level design (exact signatures, algorithms and state machines for non-trivial logic, schema and migration steps, error mapping, configuration, per-module test mapping) from a frozen SDD reconcile Build or refresh the as-built Implementation Guide from the code (API contracts, module map, control flow, data models, divergences from the SDD, a one-page Gist) plus a newcomer walkthrough with flow redesign Handle a design flaw found during implementation — stop building, record the finding, weigh options, write the decision as an ADR that supersedes the old one, attack only the delta, get the user's app remember Save a durable project learning — a decision, a correction, an anti-pattern, or a convention — as a memory that takshak re-injects at session start and design time. resume Continue interrupted takshak work from .claude/checkpoint.json — reports where it stopped, checks the budget window has reset, and picks up the literal next action. retro Structured feature retrospective once implementation finishes — diffs plan vs. review Guide a staff/lead engineer through a hardened SDD section by section instead of dumping the whole document — orientation, then Risk Register by severity, adversary pass history, amendments, and test Sdd implementer Implement an approved takshak plan task by task from its SDD, staying in the implement-bug-fix loop without process interruptions while silently staging design amendments and checkpointing. ship Gated deploy pipeline — documentation, tests, type check, independent code review, build — then Jira transitions and Slack notification. start The single entry point for development work. work Route any request that changes code (bug report, small tweak, change, feature, whole solution) into a tracked work item, and with Jira on create a ticket whose type is chosen by weighing the work (sol