Loading...
Loading...
Found 39 Skills
End-to-end project engineering — from understanding user intent to architecture design, incremental build with verification, and systematic debugging. Covers scheduled tasks (cron jobs), dashboards, web apps, APIs, scripts, and any software the user wants built. Replaces coder + preview-dev with a unified methodology.
Ask which skill or process is suitable for the current scenario; it is the router for all skills in this repository.
Implement features using tracer bullet approach - build minimal end-to-end vertical slice first, then expand.
Use this when you need to execute the AI SDLC (Spec Pack) process in the sdlc-dev repository, select/chain together skills from the demand side (raw/solution/prd/prototype/demo) and implementation side (plan/execute/finishing), and use guardrails to avoid context drift, incorrect directory writes, or skipping critical steps under pressure.
Use when solution space exploration is complete and you're ready to create an implementation plan. Enforces "simple over easy" - the fundamentally right solution, not the path of least resistance. Triggers after /design-solution, when a solution has been chosen, or when asked to "make a plan" or "create a plan".
Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Orchestrates end-to-end software development using the addyosmani/agent-skills framework. Guides the user through define → plan → build → verify → review → ship phases, spawns subagents for each step, tracks state persistently, and never loses focus on workflow completion. Use when the user says "let's build X", "help me implement X", "walk me through X", or wants structured multi-phase dev guidance. Also triggers when a task is clearly non-trivial and would benefit from phased execution.
Orchestrate a specialized software development agent team. Receive user requests, classify task type, select the matching workflow, delegate each step to specialist agents via the Agent tool, and assemble the final output. Use when the user needs multi-step software development involving architecture, implementation, testing, security review, or code review. Also use for production incident investigation — when the user reports a live system issue, service outage, pod crash, data anomaly, or needs root cause analysis using kubectl, psql, argocd, or docker. Trigger this skill whenever a task involves more than one concern (e.g., "add a new endpoint" needs BA + Architect + Developer + QA + Security), when the user mentions team coordination, agent delegation, or when the work clearly benefits from multiple specialist perspectives rather than a single implementation pass.
Meta skill for the EvanFlow system. Loads the shared vocabulary (deep modules, deletion test, vertical slice, grill, mockup quick-mode, no-auto-commit) and describes when to invoke each evanflow-* skill. Use when starting a new task and unsure which evanflow skill applies, or when you need to ground reasoning in the shared vocabulary.
Builds multi-layer features as vertical end-to-end slices instead of horizontal layers. Each slice is verified before the next begins. Use when: starting any task that spans 2+ layers (DB, API, UI, tests), building CRUD features, implementing multi-step flows, decomposing features into subtasks, or planning implementation order.
The root skill of the easysdd workflow family — introduces the workflow system and routes users to the correct sub-skill. Trigger scenarios: Users mention "easysdd", "sdd", "spec-driven", "how to use this set of processes", "which skill should I use", "where to start", or describe a new feature but haven't decided on the entry stage. Known intents (brainstorm/design/implementation/acceptance/BUG/exploration, etc.) will trigger the corresponding sub-skill first instead of this skill.