marcosathanasoulis
UserA planning skill for Claude or ChatGPT that asks before it plans. Three versions: claude.ai, engineers, and read-only for people with data access who don't ship code.
Categories
Indexed Skills (18)
prompt-it
Use when starting a substantial research or analysis task. Performs automatic proportional read-only planning and assessment; medium/large work asks "Proceed?" before any implementation. Read-only edition — research, analysis and design only, never implementation or code changes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
diagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
prompt-it-side-lane-routing
Optionally qualify Side Lane routes for a Prompt it task graph and route explicitly authorized, bounded external research reviews without changing the originating coordinator.
side-lane
Use at the start of an implementation task to discover and qualify optional model lanes, then route approved tasks through exact configured workers, including Prompt it staffing and explicit spend routing.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.