Loading...
Loading...
Found 35 Skills
SDD workflow: specs, designs, implementation plans, quality gates.
Use when approved Spec Kit `tasks.md` must be executed into implementation changes, or when task execution is blocked by sequencing/checklist gates before feature completion.
Documentation-driven project development workflow. Intelligently determines task types, executes existing plans or generates new plans using feature-dev. **Use Cases:** - Complete project documentation exists, need to execute development tasks - User specifies to execute a certain plan (e.g., "Execute plan 001") - User requests to develop new features (automatically uses feature-dev to generate plans) **Prerequisites:** - The project should already have a docs/ documentation structure (PRD, SAD, etc.) - For new projects, it is recommended to first use the project-docs-setup skill to create complete documentation - If plan formulation is needed, it is recommended to use the project-planning skill **Relationship with Other Skills:** - project-docs-setup: Creates project documentation structure - project-planning: Formulates development plans (requirement clarification + design discussion + plan writing) - project-workflow: Executes development plans + updates documentation - Recommended workflow: project-docs-setup → project-planning → project-workflow **Trigger Methods:** - "Execute plan 001" / "Continue 001-user-authentication" - "Start development" / "Execute plan" / "Continue last task"
Use when executing implementation plans with independent tasks in the current session
Execute tasks from TODO file - Generic task runner [/todo-task-run xxx]
Use when implementing a planned OpenSpec change by applying tasks and validating all artifacts.
Automate Documenso tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Postgrid Verify tasks via Rube MCP (Composio). Always search tools first for current schemas.
Interactive planning and execution for complex tasks. Use when user asks to use or invoke planner skill.
Creates Robot Framework test cases for creating and executing SnapLogic triggered tasks. Use when the user wants to create triggered tasks for on-demand pipeline execution, execute triggered tasks with parameters, or wants to see triggered task test case examples.
Explore-first wave pipeline. Decomposes requirement into exploration angles, runs wave exploration via spawn_agents_on_csv, synthesizes findings into execution tasks with cross-phase context linking (E*→T*), then wave-executes via spawn_agents_on_csv.