elzawarudo

@elzawarudo source repo

29 skills
0 followers
20 hours ago last updated

▌
Krt CI Questor · elzawarudo bundle
Investigate CI/CD failures and produce concise cause reports. Use when a user asks why a GitHub Actions, GitLab CI, CircleCI, Jenkins, or other pipeline failed; needs log triage, flaky-test assessment, runner/dependency/config diagnosis, failed-check summaries, rerun guidance, or a simple report explaining what happened and what to do next. Runtime aliases may expose this as krt:ci-questor.

0
installs
▌
Krt Repo Medic · elzawarudo bundle
Diagnose repository and skill-portfolio health and produce focused maintenance prescriptions. Use for repo health checks, maintenance audits, stale docs, broken scripts, doc/code drift, CI/test hygiene, onboarding friction, dependency risk, delivery bottlenecks, skill catalog/metadata drift, routing overlap, missing safety wiring, weak skill tests/evals, or "what should we clean up" analysis. Runtime aliases may expose this as krt:repo-medic.

0
installs
▌
Krt Jira Scribe · elzawarudo bundle
Manages Jira Server/Data Center issues on a Spanish-language instance. Verifies existing global issues and subtasks, checks whether new work belongs under an existing parent, proposes Spanish issue/subtask creation when missing, handles active sprint placement, adds PR backlinks, and manages Spanish transitions. Runtime aliases may expose this as krt:jira-scribe.

0
installs
▌
Krt Harness Wise · elzawarudo bundle
Create versionable coding harness artifacts from project documentation and agent initialization context, or diagnose and improve an existing harness. Use when a user asks to prepare a coding handoff, create/update a harness file, inspect current harness quality, or make implementation context compact before planning/work. Runtime aliases may expose this as krt:harness-wise.

0
installs
▌
Krt Rebase Smith · elzawarudo bundle
Safe workflow to keep history clean by rebasing a child branch onto develop before merging. Resolve which branch will be rebased, verify whether develop exists, support rebase --onto for branches derived from another feature branch, and if develop does not exist, ask for an alternative base branch first. Runtime aliases may expose this as krt:rebase-smith.

0
installs
▌
Krt Review Herald · elzawarudo bundle
Triage pull request review feedback, plan response work, apply approved fixes when requested, verify the result, draft clear reviewer replies, and optionally publish approved review-thread replies or resolutions. Use when a user asks to address PR comments, summarize review feedback, resolve GitHub review threads, prepare reply text, decide which comments are blocking, apply fixes from review comments, or turn review feedback into commits and responses. Runtime aliases may expose this as krt:review-herald.

0
installs
▌
Krt Skill Arbiter · elzawarudo bundle
Evaluate a KRT skill portfolio with deterministic corpus checks, supervisor-captured pass/fail/inconclusive scoring, and structural portfolio validation. Use when adding or changing skills, auditing routing and negative triggers, testing fallback/permission/restart/outcome behavior, or checking portfolio metadata and safety wiring. It does not execute models or grade its own behavior.

0
installs
▌
Krt Document Forge · elzawarudo bundle
Convert PDF and DOCX source documents into versionable Markdown artifacts for coding harnesses. Use when a user needs to extract project briefs, requirements, client notes, architecture documents, contracts, or other .pdf/.docx inputs into .md so krt-harness-wise or another planning skill can use them as harness evidence. Runtime aliases may expose this as krt:document-forge.

0
installs
▌
Krt Gitflow Knight · elzawarudo bundle
Gitflow-based commit workflow: ensure work happens on a properly named feature branch (propose/confirm branch name if missing or off-convention), split pending changes into atomic commits with clear messages, present a commit plan for user authorization, then stage and create the commits. Use when the user asks to commit changes, wants to follow gitflow, or wants help preparing commits before pushing/opening a PR. Never add any LLM co-author lines to commit messages. Runtime aliases may expose this as krt:gitflow-knight.

0
installs
▌
Krt Compound Master · elzawarudo bundle
Supports standalone and Seneschal-nested delivery with per-run state, inherited initiative contracts, and brokered decisions. Discovery-gated artifact-first orchestrator for compound-engineering product delivery. Resolves roadmap/readiness generation, runs brainstorm/plan/document-review loops, derives mergeable work packages with focused review units, executes each review unit through resolved work/code-review roles, and hands shipping to krt-release-marshal with CI break-prevention evidence. Use when turning an existing documented software project into a sequenced roadmap and PR/Jira delivery program. Runtime aliases may expose this as krt:compound-master.

0
installs
▌
Krt Deploy Summoner · elzawarudo bundle
Prepare, inspect, and diagnose deployments across Docker, Docker Compose, Helm, and Kubernetes. Use when a user asks to review deployment manifests, Helm charts or values, Dockerfiles, compose files, Kubernetes resources, rollouts, pods, logs, probes, resources, namespaces, image tags, deployment readiness, rollback plans, smoke tests, CrashLoopBackOff, ImagePullBackOff, failed Helm upgrades, or safe kubectl/helm/docker diagnostic commands. Runtime aliases may expose this as krt:deploy-summoner.

0
installs
▌
Krt Docs Chronicler · elzawarudo bundle
Maintain durable project knowledge without creating documentation sprawl. Use when a user asks to update docs after a feature, incident, release, review, or architecture decision; reconcile stale README/runbook/ADR/changelog content; capture lessons learned; write lightweight ADRs; audit documentation drift; or decide where a new piece of project knowledge belongs. Runtime aliases may expose this as krt:docs-chronicler.

0
installs
▌
Krt Release Marshal · elzawarudo bundle
Orchestrate the full delivery flow for the current project repository: direct krt-gitflow-knight for clean commits, krt-rebase-smith for clean branch history, resolve Jira Cloud or Server/Data Center explicitly, then open a GitHub pull request with bidirectional Jira/PR links. Use when the user asks to create/open a PR, prepare a pull request, ship current work, publish branch changes for review, or run the full gitflow + rebase + Jira + PR workflow. Runtime aliases may expose this as krt:release-marshal.

0
installs
▌
Krt State Archivist · elzawarudo bundle
Compact Compound Master state artifacts while preserving full historical detail in linked archive files. Use when compound-master-state.md or other Compound Master orchestration state has grown too large for efficient context loading, when Compound Master live-context entrypoints such as SKILL/router docs have become diluted, when krt-compound-master is about to resume from a long state file, after major Compound Master gates, before long closeouts, or when the user asks to clean, compact, archive, trim, or curate Compound Master generated documents.

0
installs
▌
Krt Swarm Seneschal · elzawarudo bundle
Coordinate explicitly requested multi-worker delivery through dependency-aware planning, isolated worker waves, reconciliation, and release handoff. Use for swarm orchestration, parallel Codex workers, or multiple nested krt-compound-master runs. Do not use for one execution-ready task, generic project planning, Jira administration, or release management.

0
installs
▌
Krt Interface Warden · elzawarudo bundle
Independently design or implement distinctive, functional frontend interfaces using Editorial Product UI: content-led hierarchy, working-surface metaphors, deliberate layout archetypes, restrained containers, purposeful typography, and accessible code. Use for visual direction, redesign, polish, or implementation when a screen risks generic AI/SaaS cards, dashboard templates, unnecessary tables, weak hierarchy, or decorative chrome; honor a krt-frontend-ux-guardian contract and consume a krt-interface-inquisitor brief when supplied, without requiring either companion.

0
installs
▌
Krt Word Illuminator · elzawarudo bundle
Create, edit, inspect, render, compare, validate, and privacy-scrub professional Microsoft Word DOCX documents. Use for reports, proposals, letters, minutes, manuals, articles, and other .docx deliverables that require semantic Word styles, template preservation, grounded content, tables or figures, accessibility checks, metadata hygiene, and mandatory visual QA before final delivery.

0
installs
▌
Krt Jira Cloud Scribe · elzawarudo bundle
Manages Jira Cloud issues in Spanish using REST API v3, Basic Auth with email plus API token, project-local cloud env files, Atlassian Document Format payloads, active sprint placement, PR remote links, and localized workflow transitions. Use when the target Jira instance is Atlassian Jira Cloud rather than Jira Server/Data Center, especially for creating or reusing issues/subtasks, adding GitHub PR backlinks, moving issues through review/done states, or preparing Jira handoff context for KRT release workflows.

0
installs
▌
Krt Security Sentinel · elzawarudo bundle
Review security-sensitive slices/work packages and diagnose repositories, systems, and agentic workflows for cybersecurity risk. Use for application security, threat/risk assessment, auth/authz, tenant isolation, secrets, API or supply-chain security, infrastructure posture, incident diagnosis, secure-by-design checks, Compound Master security gates, or AI-agent risks such as prompt/goal hijacking, tool misuse, authority escalation, identity/scope errors, memory poisoning, untrusted-content propagation, exfiltration, and runaway budget loops. Runtime aliases may expose this as krt:security-sentinel.

0
installs
▌
Krt Delivery Navigator · elzawarudo bundle
Turn validated software requirements into a practical project delivery plan. Use when a user has a requirements packet, especially one produced by krt-requirements-weaver, and needs project planning artifacts such as scope framing, major tasks, prioritized backlog, milestones or iteration slices, schedule outline, team responsibilities, technology choices, dependencies, risks, and partial deliveries. Also use when the user asks how to build the system, how to organize the work, how to phase delivery, or how to plan the backlog before implementation. Runtime aliases may expose this as krt:delivery-navigator.

0
installs
▌
Krt Bicentennial Writer · elzawarudo bundle
Writing and editing guidance for natural, specific, contextual prose that avoids generic patterns associated with AI-generated writing. Use when the user asks to draft, rewrite, humanize, naturalize, polish, localize, or audit text so it sounds less formulaic; when working on theses, academic articles, research documents, academic reasoning, critical argument, or AI-assisted authorship; or when they mention "sounds like AI," "AI detector," "humanize text," "natural writing," "human tone," "AI writing tells," "Bicentennial Writer," "suena a IA," "detector de IA," "humanizar texto," "redacción natural," or "tono humano," or want to avoid typical AI-writing patterns in Spanish or English. Runtime aliases may expose this as krt:bicentennial-writer.

0
installs
▌
Krt Requirements Weaver · elzawarudo bundle
Clarify rough software requirements before planning or coding. Use when a user shares a client brief, classroom prompt, feature request, meeting notes, RFP, or partial specification and needs help to analyze the problem, identify stakeholders, identify requirement gaps, ask focused elicitation questions, refine functional and non-functional requirements, rewrite vague statements into testable ones, surface assumptions and open questions, and validate scope and acceptance criteria with stakeholders. Runtime aliases may expose this as krt:requirements-weaver.

0
installs
▌
Krt Cognitive Load Court · elzawarudo bundle
Diagnose avoidable cognitive workload in software task flows through six independent lenses covering memory, search, integration, decision, uncertainty, and recovery. Use when asked to audit cognitive load or mental effort, compare workflow variants, investigate an interface that feels mentally taxing, or verify that a redesign reduced workload. Do not use for broad product-polish audits or clinical cognitive assessment.

0
installs
▌
Krt Frontend UX Guardian · elzawarudo bundle
Guard frontend work toward functional, accessible, responsive, task-centered UX/UI and browser-verified quality. Use independently when building, changing, or functionally reviewing apps, dashboards, tools, forms, data tables, editors, landing pages, or interactive surfaces; optionally coordinate with krt-interface-inquisitor for adversarial visual critique or krt-interface-warden for distinctive visual direction.

0
installs
▌
Krt Interaction Polisher · elzawarudo bundle
Audit and refine the temporal, tactile, and perceived-performance quality of frontend interactions. Use when an implemented app feels dead, abrupt, sluggish, fragile, or insufficiently polished; when reviewing buttons, forms, menus, overlays, navigation, drag-and-drop, asynchronous mutations, loading and success states, animation, microinteractions, keyboard feedback, or reduced-motion behavior; or when a serious product needs implementation-ready interaction critique or focused fixes without a visual redesign.

0
installs
▌
Krt Interface Inquisitor · elzawarudo bundle
Independently critique frontend interfaces with adversarial Editorial Product UI rigor, identifying generic AI/SaaS patterns, unjustified cards or tables, weak typographic hierarchy, excessive surfaces, layout-archetype drift, and concrete implementation changes. Use for visual audits, review requests, or critique-and-fix workflows; consume krt-frontend-ux-guardian constraints when supplied and produce a brief that krt-interface-warden or any implementation workflow can use, without requiring either companion.

0
installs
▌
Krt Roadmap Cartographer · elzawarudo bundle
Generate exactly one roadmap or readiness report for a documented initiative. Validates context sufficiency, maps source-backed roadmap items, dependencies, waves, and branch/PR strategy, or blocks with actionable readiness guidance. Use when a user needs a roadmap before compound delivery, or when krt-compound-master resolves its required roadmap_generator role. Runtime aliases may expose this as krt:roadmap-cartographer.

0
installs
▌
Krt Product Polish Council · elzawarudo bundle
Orchestrates a comprehensive, evidence-based polish audit of web, mobile, and desktop applications through a versioned atlas, a cartographer, and twelve evaluators, with a required cognitive-load overlay on every finding. Use when asked to polish an application, assess its product maturity, walk end-to-end flows, find rough seams or amateur behavior, produce a prioritized improvement backlog, or verify that a round of changes raised perceived quality.

0
installs
▌
Krt Real World Edge Testing · elzawarudo bundle
Build and safely execute evidence-backed edge-case campaigns across real system boundaries. Use for adversarial or failure-mode testing that needs deterministic fixtures, strong oracles, preflight, and recovery—not narrow unit tests, coverage review, penetration testing, or open-ended chaos engineering. Runtime aliases may expose this as krt:real-world-edge-testing.

0
installs

29 published skills