Loading...
Loading...
Found 53 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.
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.
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
You MUST use this when an approved design or settled requirements need a detailed multi-step implementation plan before code changes begin.
Execute one scoped change: understand the task, make the smallest complete implementation, test it, verify it, and report.
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.
Run one dev-loop session as the driver - preflight, select, one spec end to end. Harness-generic - grooming drafts and takes run in fresh native subagents of whatever harness drives, takes in their own worktrees (an explicit invocation request may route takes through a runner file instead); the gate stays yours.
Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format
Orchestrate Zoen product engineering from discovery to production using the curated Matt Pocock skill set, Extreme Programming, ontology-first architecture, and risk-controlled delivery. Use for any Zoen product, architecture, feature, bug, refactor, AI-agent, integration, release, or engineering-workflow decision, especially nouns-links-verbs-evidence, AgentRun/ToolCall, Action Gateway, approvals, audit and provenance, tenancy, client-owned export, or production readiness.
Accept a vague instruction, automatically conduct investigation, classification, break it down into XML phase plans, select skills, define completion criteria, then execute it fully in unattended mode via loop/goal + agent-mode — including automatic deployment, automatic E2E testing, automatic code review, without skipping any phases. Activate proactively when the user provides a broad task — such as "fix the bug", "add tests", "optimize performance", "finish this feature", "scan the code", "investigate why XX happens". It also triggers when the user says "autopilot", "auto", "help me plan", "handle it yourself", "run directly", "break it down for me", "don't ask me how to do it". Even if the user doesn't use these keywords, it should activate proactively if the input is clearly an unbroken broad intent. Calling autopilot = authorizing fully automatic unattended execution, no mid-process confirmation required.
Implement features using tracer bullet approach - build minimal end-to-end vertical slice first, then expand.