tikalk
- 54 skills
- 0 followers
- 145 repo stars
- yesterday last updated
- ▌ Factory Tickets · tikalk bundleUse when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.
- ▌ Architect Boot · tikalkUse when architecture work starts or a tech-stack or pattern decision emerges — injects the project ADR index (docs/adlc/memory/adr/, legacy .adlc/memory/adr/ fallback) as session context and suggests the decision for capture via /architect-specify (never writes drafts itself); invoked from team-boot's Class Boots catalog.
- ▌ Writing Skills · tikalk bundleUse when creating a new skill, editing an existing skill, or verifying skills work before deployment
- ▌ Tech Radar Boot · tikalk bundleUse when choosing or evaluating a technology (framework, database, library, cloud tool) — injects Tikal Israeli Tech Radar context (adoption ring, quadrant, opinion, Keep/Start alternatives for Stop items) from the adlc-radar OKF knowledge repository, and pairs the selection with ADR capture via /architect-specify; invoked from team-boot's Class Boots catalog (formerly tech-radar-context).
- ▌ Factory Orchestrator · tikalkUse when work arrives at the software factory at any lifecycle stage — a new request, an informational question, a CI failure on a delivered PR, review findings, a merge notification, or a reply to a factory question — and must be routed to the right factory skill, human gate, or follow-up context.
- ▌ Change Specify · tikalk bundleUse when a change rationale just emerged — a revert, hotfix, fix chain, workaround, or abandoned approach — and you want guided facilitation (options, consequences, provenance) before it becomes a ChDR. Not for mining git history (/change-init) or reviewing drafts (/change-clarify); class boots only suggest this skill, they never write drafts.
- ▌ Factory Clean · tikalkUse when the user asks to reclaim project disk space or clean up leftovers — inventories worktrees, containers, dependencies, and processes, reclaiming only user-approved items; read-only by default.
- ▌ Factory Learn · tikalkUse when coordinating continuous improvement loops (team-levelup + change + evals feedback + cleanup) targeting team-ai-directives — includes build-to-delete pruning and promote-to-check.
- ▌ Factory Queue · tikalkUse when managing mission brief intake — triage, AI-assisted advisory scoring, gating label stamping, and milestones or epics generation (plan mode).
- ▌ Factory Setup · tikalk bundleUse when configuring the factory tracker provider for a repo (first factory run, missing .adlc/issues-provider.yml), verifying provider wiring, or switching trackers.
- ▌ Factory Intent · tikalk bundleUse when orchestrating an intent lifecycle (product + architecture lanes, two scope-pinned gates, joint build-and-verify) to generate PRD.md and AD.md from one Mission Brief.
- ▌ Factory Review · tikalk bundleUse when reviewing PRs for severity-ranked policy compliance against REVIEW.md, babysitting agent PRs to merge, or self-healing Important findings before a human sees them.
- ▌ Factory Mission · tikalk bundleUse when executing a spec-gated mission from the queue — inner loop specify → plan → implement ↔ converge with tracker integration, worktree isolation, and a circuit breaker.
- ▌ Factory Release · tikalk bundleUse when an approved PR head must reach production through a gated release — exact-head merge, staged canary rollout with threshold verdicts, a SemVer-tagged release with notes, milestone close and roadmap update, plus a monitor handoff. Triggers on post-merge rollout work; not for continuous monitoring, review depth, or infra provisioning.
- ▌ Factory Runbook · tikalk bundleUse when a factory run must post its changes — check out the run branch, commit a step's allowlisted paths, push only that branch, and open or reuse one draft MR/PR with milestone/assignee ownership. Also the shared home for factory run contracts (executor, tracker integration, lanes, brief and provider templates).
- ▌ Team Init · tikalk bundleUse when bootstrapping team knowledge from a brownfield codebase — reverse-engineers CDRs for contribution to team-ai-directives adlc branch.
- ▌ Team Levelup · tikalk bundleUse when a session ends to extract CDRs, score confidence, batch review, and publish accepted CDRs to team-ai-directives. Auto-triggers on session_end event. Also invoked from team-boot's Class Boots catalog for CDR descriptor matches.
- ▌ Change Boot · tikalkUse when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr/chdr.md, legacy .adlc/memory/chdr.md fallback) as session context; pairs history mining (/change-init) with in-session capture suggested via /change-specify (never writes drafts itself), clarified via /change-clarify; invoked from team-boot's Class Boots catalog.
- ▌ Team Diagnose · tikalkUse when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion.
- ▌ Factory Init · tikalkUse when onboarding a brownfield repo onto ADLC end-to-end, or running the recurring PDR↔ADR↔ChDR↔code alignment sweep (--refresh).
- ▌ Product Boot · tikalkUse when product or feature work starts, or a PDR-worthy decision (scope, persona, monetization) emerges — injects the PDR index (docs/adlc/memory/pdr/, legacy .adlc/memory/pdr/ fallback) as session context and suggests the decision for capture via /product-specify (never writes drafts itself); invoked from team-boot's Class Boots catalog.
- ▌ Workspace · tikalk bundleMulti-repo workspace coordinator for shared team context. Initialize .adlc/ structure, configure .gitignore, discover child repos, link them as Git submodules, and audit workspace health. Use --init for first-time setup, default mode for ongoing auditing.
- ▌ Mission Brief · tikalk bundleMission-driven SDD orchestrator: take a feature description, structure it into a Mission Brief (goal, constraints, success criteria), generate an ordered step list with prompts that trigger installed SDD skills via model invocation or command-file discovery, and walk those steps to converged implementation. Use when you want an end-to-end specify → plan → implement ↔ converge loop with gates, a circuit breaker, resume, and an audit trail — without YAML files or per-framework profiles.
- ▌ Team Boot · tikalk bundleBootstrap the session with team AI directives context (constitution, CDR index, PDR/ADR/ChDR indexes, skill registry). Runs automatically at session start via the event hook.
- ▌ Team Setup · tikalk bundleInteractive setup of team AI directives. Use when bootstrapping a team directives repository from scratch, cloning an existing one, pointing to a local path, or checking an existing configuration. Auto-invoked by team-boot when a project has no configured team AI directives (self-install), and available on demand via /team-setup.
- ▌ Evals Init · tikalk bundleInitialize evals/{system}/ directory structure for evaluation system following EDD principles (Standalone). Choose PromptFoo or DeepEval based on tech stack, generate security baseline.
- ▌ Team Repair · tikalk bundleRe-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives health validation.
- ▌ Team Skills · tikalk bundleBrowse and install team skills from the team AI directives. Use when listing, adding, or onboarding team skills to the current agent's skills directory. Supports --all to install every default and external skill at once.
- ▌ Change Init · tikalk bundleMine git history for Change Decision Records (ChDRs) by detecting commit messages that link to issue trackers, clustering the commits into change stories, and inferring the decisions behind them. Use when bootstrapping project memory from an existing repo's history (brownfield), before refactoring unfamiliar code, or to recover rationale that was never documented.
- ▌ Team Discover · tikalkManually re-scan team context modules and produce a structured discovery table with relevance assessments. The CDR index is already in the system prompt; use this for explicit re-discovery.
- ▌ Evals Analyze · tikalk bundleAnalyze evaluation results and close the loop. Specification failures create local CDRs to fix agent rules; generalization failures go to evaluator backlog.
- ▌ Evals Clarify · tikalk bundleRefine, cluster, and accept draft criteria into the published goldset. Isolates 20% holdout split and publishes goldset.md + goldset.json.
- ▌ Evals Specify · tikalk bundleExtract eval criteria from product specs and production failure traces (bottom-up error analysis). Writes proposed criteria to .adlc/drafts/evals/.
- ▌ Evals Validate · tikalk bundleRun evaluations and validate evaluator quality (SLA compliance, TPR/TNR, statistical accuracy). Executes PromptFoo or pytest DeepEval.
- ▌ Levelup Init · tikalk bundleReverse-engineer Context Directive Records (CDRs) from an existing codebase for contribution to team-ai-directives. Use when bootstrapping team knowledge from brownfield projects.
- ▌ Product Init · tikalk bundleReverse-engineer Product Decision Records (PDRs) from an existing codebase and documentation using multi-agent feature-area analysis (brownfield). Use when documenting product decisions inferred from an already-built product.
- ▌ Change Clarify · tikalk bundleReview, accept, reject, or defer Change Decision Records (ChDRs) discovered by change-init. Interactive one-ChDR-at-a-time workflow that validates inferred decisions against their git/issue evidence before promotion to project memory.
- ▌ Change Publish · tikalk bundlePromote accepted Change Decision Records (ChDRs) from drafts to project memory at .adlc/memory/chdr/, write OKF-style frontmatter, and regenerate the boot-facing .adlc/memory/chdr.md index that team-boot injects at session start. Use after /change-clarify has accepted ChDRs.
- ▌ Evals Implement · tikalk bundleGenerate executable graders and configs from goldset. Generates Python graders / metrics and auto-runs unit tests to verify grader correctness.
- ▌ Team Constitution · tikalk bundleInteractively create or amend the team constitution in team-ai-directives. Use when bootstrapping a new team AI directives, establishing team-wide principles for the first time, or amending existing ones.
- ▌ Levelup Clarify · tikalk bundleReview, accept, reject, or defer Context Directive Records (CDRs) discovered by levelup-init or proposed by levelup-specify. Interactive one-CDR-at-a-time workflow.
- ▌ Levelup Publish · tikalk bundleCompile accepted Context Directive Records (CDRs) into team-ai-directives artifacts and create a draft PR. Builds context modules, evals goldensets, and/or skills based on CDR context types.
- ▌ Levelup Specify · tikalk bundleExtract Context Directive Records (CDRs) from the current session after completing work. Identifies reusable patterns (rules, personas, examples, evals) and captures directive compliance cases for team-ai-directives.
- ▌ Product Analyze · tikalk bundleRead-only analysis of PDR↔PRD consistency, PDR quality, cross-PDR conflicts, and staleness. Outputs a structured markdown report with severity-assigned findings. Use after /product-implement or periodically to detect drift.
- ▌ Product Clarify · tikalk bundleRefine and validate Product Decision Records through targeted clarification questions. Review PDR completeness, detect conflicts, approve decisions, and update status to Accepted. Use before /product-implement.
- ▌ Product Roadmap · tikalk bundleTrack milestone progress across four layers of truth — decision state (PDR status), execution state (live issue tracker via MCP), evidence state (code-vs-PDR verification), and gate state (milestone gates). Shows honest completion, done-means warnings, and updates status only when all layers are green. Use for weekly progress checks and milestone validation.
- ▌ Product Specify · tikalk bundleInteractive PRD exploration and Product Decision Record (PDR) creation for greenfield products. Facilitates product discovery discussions, surfaces trade-offs, and documents decisions as individual PDR files. Use when starting a new product or major pivot.
- ▌ Architect Init · tikalk bundleReverse-engineer architecture from an existing codebase to create ADRs documenting discovered decisions. Use when bootstrapping architecture documentation for brownfield projects.
- ▌ Product Implement · tikalk bundleGenerate a full Product Requirements Document (PRD.md) from accepted PDRs using multi-agent DAG orchestration. Reads individual PDR files, generates PRD sections from templates, validates output, and promotes accepted PDRs to memory. Use after /product-clarify.
- ▌ Architect Analyze · tikalk bundleAnalyze architecture for consistency between ADRs and AD, completeness, and quality issues. Use when validating generated or refined architecture artifacts, before feature development, during architecture review, or periodically to detect drift.
- ▌ Architect Clarify · tikalk bundleRefine and validate system-level ADRs through targeted clarification questions. Use when ADRs need review, gaps need filling, or ADR status must be approved before architecture generation.
- ▌ Architect Specify · tikalk bundleInteractive PRD exploration and system-level ADR creation for greenfield projects. Use when transforming a PRD or high-level system description into Architecture Decision Records.
- ▌ Architect Implement · tikalk bundleGenerate a full Architecture Description (AD.md) from accepted ADRs using multi-agent DAG orchestration. Use when accepted ADRs exist and you need to produce or update unified architecture documentation.
- ▌ Tech Radar Context · tikalk bundleDiscover and inject Tikal Israeli Tech Radar context — adoption ring, quadrant, and Tikal's opinion — for any technology, framework, database, library, or cloud tool implied by the current prompt. Model-invoked whenever a tech stack choice is being made or evaluated, similar to team-discover but scoped to the Tikal Tech Radar.