Loading...
Loading...
Found 8 Skills
Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).
Create and validate implementation plans (PLAN). Use when planning implementation phases, defining tasks, sequencing work, analyzing dependencies, or working on plan files in .start/specs/. Generates per-phase files (plan/README.md + plan/phase-N.md) for progressive disclosure. Includes TDD phase structure and specification compliance gates.
Scaffold or continue a software project with a Harness-style workflow. Use when the user wants a new app or repo, a structured bootstrap, or milestone-driven execution from PRD through implementation. Supports greenfield and existing codebases across web, iOS, CLI, agent, and desktop projects.
Minimal SPARV workflow (Specify→Plan→Act→Review→Vault) with 10-point spec gate, unified journal, 2-action saves, 3-failure protocol, and EHRB risk detection.
Provides project management, task tracking, team coordination, and project delivery capabilities. Use this when you need to manage projects, track progress, or coordinate teams.
Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.
Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.