tikalk
24 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
tikalkarchitect-analyze
Use when validating generated or refined architecture artifacts, before feature development, during architecture review, or periodically to detect ADR↔AD drift, completeness gaps, and quality issues.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkarchitect-boot
Use 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 pairs the decision with capture via /architect-specify; invoked from team-boot's Class Boots catalog.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkchange-clarify
Use when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project memory.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkchange-publish
Use when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkevals-analyze
Use when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkfactory-architect
Use when orchestrating an architecture lifecycle (specify/init → clarify → implement → analyze) to generate or maintain AD.md.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkfactory-clean
Use 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.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkfactory-init
Use when onboarding a brownfield repo onto ADLC end-to-end, or running the recurring PDR↔ADR↔ChDR↔code alignment sweep (--refresh).
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkfactory-learn
Use when coordinating continuous improvement loops (team-levelup + change + evals feedback + cleanup) targeting team-ai-directives — includes build-to-delete pruning and promote-to-check.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkfactory-review
Use 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.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkfactory-tickets
Use 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.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkproduct-analyze
Use when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkproduct-implement
Use when accepted PDRs exist and PRD.md must be generated or updated.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkproduct-init
Use when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkproduct-specify
Use when you want guided trade-off analysis, multi-option comparison, or structured product decision facilitation before documenting. Optional for routine capture — team-boot writes lightweight PDR drafts directly.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-boot
Use when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index, Class Boots catalog, skills registry — is not yet injected; also fires the session-end friction trigger for CDR/ADR/PDR capture with pending-decision safety nets.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-constitution
Use when bootstrapping a new team AI directives repo, establishing team-wide principles for the first time, or amending the constitution in team-ai-directives.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-discover
Use when explicit manual re-discovery of team context modules is wanted beyond the injected CDR index (/team-discover) — produces a structured match table with relevance assessments.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-init
Use when bootstrapping team knowledge from a brownfield codebase — reverse-engineers CDRs for contribution to team-ai-directives adlc branch.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-levelup
Use when a session ends to extract CDRs, score confidence, batch review, and publish accepted CDRs to team-ai-directives. Auto-triggers on sessionend event. Also invoked from team-boot's Class Boots catalog for CDR descriptor matches.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-setup
Use when bootstrapping a team directives repository from scratch, cloning an existing one, pointing to a local path, or checking an existing configuration.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-skills
Use when listing, adding, or onboarding team skills from the directives repo to the agent's skills directory; --all installs every default and external skill at once.
- instalaciones
- 2
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkarchitect-init
Use when bootstrapping architecture documentation for a brownfield project by reverse-engineering ADRs from an existing codebase.
- instalaciones
- 1
- GitHub Stars
- 142
- Actualizado
- 20 oct
tikalkteam-diagnose
Use 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.
- instalaciones
- 1
- GitHub Stars
- 142
- Actualizado
- 20 oct