Loading...
Loading...
Found 6,342 Skills
Update project documentation after feature approval. Creates/updates feature docs and user guides. Use after /test passes and user approves. Supports task IDs for easier invocation.
Implement Beads work items from a bead id. Use when the user runs $beads-implement <bead-id> or asks to implement a bead/epic; if it is an epic, implement all sub-tasks, committing after each one and only interrupting when blocked or a decision is needed.
Verify AI claims against source documents using the DeepCitation API
Priority Judgment Assistant - Help users determine priorities from chaotic to-do items and figure out what to do right now. Triggered when users say "I have a lot of things to do", "Help me sort this out", "Set priorities", "What should I do today".
Plan and file goals and feature issues through conversation. Use when the user wants to create goals, plan features, file issues, or discuss what to build next.
Use when running Ralph-style iterative autonomous development. Triggers on /ralph or /loop commands, when autonomous iterative development is needed, when a project has specs and an implementation plan ready for iterative execution, or when deterministic context loading with subagent delegation and dual-condition exit gates is required. Orchestrates PLANNING, BUILDING, and STATUS cycles.
Run Gemini CLI to take a screenshot for a specific page.
Apply `wbfy` to the current repository.
Solve CRM integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Solve CRM data.
Customer.guru integration. Manage Persons, Organizations, Deals, Leads, Projects, Pipelines and more. Use when the user wants to interact with Customer.guru data.
Enter this sub-process when developing new features — turn the vague idea of "adding X capability" into a closed-loop acceptance process, with solution files archived so that both AI and users can later check what was thought and why decisions were made at that time. Trigger scenarios are focused on new capabilities ("develop new features", "add X", "implement XX") and do not address bugs in existing code. This skill only handles routing, deciding which next step to take among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing ones, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to latest code status)/ `check` (review without modification, generate issue list). The `check` mode has three sub-objectives: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `codestable/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down this module structure", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when an architecture action is required before proceeding during the feature-design / feature-acceptance / implement phases.