Loading...
Loading...
Found 46 Skills
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.
General software development best practices covering code quality, testing, security, performance, and maintainability across technology stacks
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
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.
Clarify the user’s intent for vague, incomplete, or ambiguous clauses, statements, and requirements before modifying the code.
Agent skill for code-goal-planner - invoke with $agent-code-goal-planner
AI SDLC repository spec-driven development workflow. Use when an AI assistant receives a medium or large feature, refactor, API change, architecture change, provider integration change, or any request that must follow requirements, design, test cases, QA planning, tasks, implementation, and validation. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution.
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.
Brainstorming socratique AVANT de coder - clarifier le problème par questions ciblées plutôt que sauter à la solution. Use when requirements are ambiguous or before starting a non-trivial feature.
Before adding abstraction, asks "do we need this now?" Activates when proposing factories, abstract classes, config-driven behavior, or "for future extensibility." Resists over-engineering. Three similar lines are better than a premature abstraction.
Integrate development-related requirement convergence, structured review, execution ruling and resumption closure into a fully automatically advancing workflow harness