cast-skills

Project and feature planning with 4 adaptive phases - Specify, Design, Tasks, Execute. Auto-sizes depth by complexity. Creates atomic tasks with verification criteria, atomic git commits, requirement traceability, and persistent memory across sessions. Stack-agnostic. Use when (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification and atomic commits, (5) Quick ad-hoc tasks (bug fixes, config changes), (6) Tracking decisions/blockers/deferred ideas across sessions, (7) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "quick fix", "quick task", "pause work", "resume work". Do NOT use for architecture decomposition analysis (use architecture skills) or technical design docs (use create-technical-design-doc).

Use when the user runs /skill-creator or asks to "set up project skills", "create

Use after finishing a non-trivial feature or change (not a trivial tweak like a rename, version bump, or typo), or whenever the user asks to "explain what you did", "how does this work", "walk me through it", "explain like I'm five", "under the hood", "why did you do it that way", "me explica", "como funciona", or "por que". Also use when the user wants a written or visual (HTML) walkthrough of a change, saved to study later. Produces a deep, beginner-friendly explanation file with diagrams, analogies, and references in a gitignored explanations/ folder.

Use at the START of any feature, fix, refactor, or change in a project. Checks for the project's skill tree (skills/project-context and skills/spec-driven-development), loads project context, and routes the task into the project's spec-driven workflow. If no project skills exist, offers once to create them with /skill-creator. Triggers on "add a feature", "implement", "fix", "refactor", "build", "change", "new endpoint", "new module", or starting any development task.