Loading...
Loading...
Found 292 Skills
Provides reflective questioning framework to challenge assumptions about work completeness, catching incomplete implementations before they're marked "done". Use before claiming features complete, before moving ADRs to completed status, during self-review, or when declaring work finished. Triggers on "is this really done", "self-review my work", "challenge my assumptions", "verify completeness", or proactively before marking tasks complete. Works with any type of implementation work. Enforces critical thinking about integration, testing, and execution proof.
Automated SYS generation from ADR decisions - generates system requirements with REQ-Ready scoring
Geração de mensagens de commit padronizadas com emoji e tipo semântico
Scaffold and maintain a reusable research → design → plan → orchestrate → act folder for any non-trivial work — software features, marketing campaigns, org changes. Drops a domain-agnostic spine (00-README · 01-plan · 02/03 research · 04-discussion newest-first · 05-tracking · 09-orchestration · artifact/board.html plan-board) plus stateless action-skills that augment the docs in place without clobbering hand-written prose. Composes ikenga-artifact-builder, huashu-design, frontend-design, ikenga-pkg-builder when present; degrades gracefully when not. Profile-driven: `software` (rich default, code work), `general` (lean, non-code — campaigns, org changes), and `content` (editorial/marketing with key art). TRIGGER when the user asks to start a real plan for non-trivial work ("plan a feature," "scaffold a plan folder," "set up groundwork for…"), references an existing plans/ folder by groundwork structure, or runs any of these actions: groundwork init / research / design / review / clarify / orchestrate / refresh-board / refresh-living-spec / status. DO NOT TRIGGER for one-off code changes, single-document writeups, ADRs, or content that fits in a single markdown file — those don't need a multi-doc plan folder. If the user just wants a single artifact (dashboard, mockup), route to ikenga-artifact-builder instead.
Provides comprehensive guidance for creating Mermaid diagrams. Mermaid is a JavaScript-based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. The main purpose of Mermaid is to help documentation catch up with development. Mermaid is particularly well-suited for use in Markdown documents, GitHub, GitLab, wikis, blogs, and other Markdown-based platforms. Use when the user wants to draw, create, generate, make, build, or visualize any diagram, chart, graph, flowchart, architecture diagram, sequence diagram, class diagram, state diagram, Gantt chart, mindmap, timeline, or any other visual diagram in Markdown-friendly format. This skill covers all 23+ Mermaid diagram types including flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, pie charts, quadrant charts, Git graphs, C4 diagrams, mindmaps, timelines, and more. Always use this skill when the user mentions Mermaid, needs diagrams for Markdown documentation, or wants quick diagrams that render directly in Markdown renderers.
Use when developing astrology/numerology apps, validating chart calculations (timezone/DST, quadrant handling), or producing psychology-first interpretations. Expert advisor (30+ years) catches common bugs (D026-D028) and defines accuracy/test standards. (project)
Build a 4-quadrant empathy map (Says, Thinks, Does, Feels) to synthesize user research into actionable insights. Use when you need to quickly capture and share user understanding across the team.
Use ShadRadioGroup and ShadRadio for single-choice options; ShadRadioGroupFormField for forms. Use when adding radio buttons or single-select options in a Flutter shadcn_ui app or ShadForm.
Synthesize a PRD (Product Requirements Document) for a big new feature. Synthesis (not interview) — uses existing project context and explicit ADRs. Asks before gh issue create. Use when scoping a substantial new feature in PRD shape (e.g., before a sprint).
Revisar um contrato contra o playbook de negociação da organização — sinalizar desvios, gerar redlines e fornecer análise de impacto de negócios. Use ao revisar acordos com fornecedores ou clientes, ao precisar de análise cláusula por cláusula contra posições padrão, ou ao preparar estratégia de negociação com redlines priorizadas e posições de fallback.
Generate FEATURES.md at the repo root by reading CONTEXT.md and docs/adr/, then enumerating the user-facing features the domain implies. Use after /grill-with-docs has settled the domain language and before /to-prd writes per-feature specs. Bridges the product→engineering gap between domain understanding and feature specification — the missing step that mattpocock's chain doesn't cover natively.
Guides data center design and build execution—site and tier selection, capacity and density planning (kW/rack, floor loading), power and cooling architecture, physical layout and containment, network meet-me and carrier connectivity, standards alignment (TIA-942, Uptime tiers), contractor coordination, commissioning, and operational handoff (DCIM, monitoring). Use when planning a new or expanded colo/on-prem facility, reviewing MEP and rack layouts, sizing power/cooling for GPU or HPC density, running DC build phases, or accepting a hall from design—not for cloud VPC/IaC (infrastructure-engineer), K8s deploy (cluster-deployment-engineer), ADRs (senior-system-architecture), GRC-only (cybersecurity), compute utilization (data-center-compute-supply-efficiency), DC portfolio (data-center-portfolio-planning-execution-lead), or capacity delivery schedule (senior-data-center-capacity-delivery-manager).