Loading...
Loading...
Found 176 Skills
Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices). L2 Worker in ln-100-documents-pipeline.
Devil's advocate. Seek contrary evidence before locking in. Use when about to make a significant decision, when confidence is high but stakes are higher, or when the team is converging too quickly.
Agent skill for v3-queen-coordinator - invoke with $agent-v3-queen-coordinator
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
Creates 4 core project docs (requirements.md, architecture.md, tech_stack.md, patterns_catalog.md). L3 Worker invoked by ln-110-project-docs-coordinator. ALWAYS created.
Guide architectural design decisions for software systems. Use this skill when designing new systems, evaluating architecture trade-offs, or creating technical design documents. Helps produce clear, well-structured design artifacts including component diagrams, data flow, and decision records.
Use this skill when writing, reviewing, or improving internal engineering documents - RFCs, design docs, post-mortems, runbooks, and knowledge base articles. Triggers on drafting a design proposal, writing an RFC, creating a post-mortem after an incident, building an operational runbook, organizing team knowledge, or improving existing documentation for clarity and completeness.
Fresh-subagent-per-task execution with two-stage review (ADR compliance + code quality). Use when an implementation plan exists with mostly independent tasks and you want quality gates between each. Use for "execute plan", "subagent", "dispatch tasks", or multi-task implementation runs. Do NOT use for single simple tasks, tightly coupled work needing shared context, or when the user wants manual review after each task.
Reviews code for quality — architecture conformance, anti-patterns, performance issues, maintainability. Read-only analysis that detects circular dependencies, N+1 queries, dead code, naming violations, and layering breaches. Use when the user asks for a code review, wants feedback on code quality, PR review, tech debt analysis, or architecture conformance checks.
arc42 architecture documentation template and guidance
Enforcement skill for consistent documentation standards
Collaborative design phase for feature lifecycle: explore requirements, discuss trade-offs, produce design document. Use when starting a new feature that needs design before implementation. Use for "design feature", "let's think through", "explore approaches", or "/feature-design". Do NOT use for simple bug fixes or tasks that don't need design discussion.