Loading...
Loading...
Found 73 Skills
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
Quickly create a task in Ralph's local backlog (ralph/backlog/) without the full PRD process. Use when user wants to add a quick task, bug, or small piece of work to the Ralph backlog, or mentions "draft task".
Query the list of project workflow statuses
Use after research (Z01 files exist) to create implementation plan - follow structured workflow
Initializes Python projects, manages dependencies, pins Python versions, and runs scripts with uv. Use when adding/removing packages, syncing environments, running tools with uvx, or building distributions.
Generate Ralph-compatible prompts for entire projects from scratch. Creates comprehensive prompts with architecture phase, implementation phases, testing, and documentation. Use when building complete applications, libraries, CLI tools, or any greenfield project requiring end-to-end development.
Serial collaborative planning with Plan Note - Multi-domain serial task generation, unified plan-note.md, conflict detection. No agent delegation.
Manages a GitHub Project board + Issues as the source of truth for product backlog, tasks, stories, and bugs. Provides three flows: bootstrap (/track-init), track (/track), and query (/backlog). Uses gh CLI for project operations and MCP tools for issue creation. Trigger: /track-init, /track <description>, /backlog, "qué tenemos pendiente?", "what's pending?", "acordate que hay que...", "remember to...", or when SDD generates tasks via sdd-tasks.
Phase 3 of the feature workflow – Complete the acceptance closed loop. Two tasks: First, check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; if deviations are found, fix them immediately instead of just "noting them down" in the report. Second, integrate this feature into the project's overall architecture documentation. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Predecessor dependency easysdd-feature-implement must be completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Manages deferred/blocked work items as GitHub Issues with labels and blocker tracking
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
Use when a technical question needs a real experiment to answer, to generate a structured spike spec before executing it in a separate session