Loading...
Loading...
Found 442 Skills
Syntax reference for Backlog notation (Backlog記法), the native markup syntax for Nulab Backlog. Covers headings, lists, tables, text styling, links, code blocks, and other formatting elements.
build
Notion integration. Manage project management and document management data, records, and workflows. Use when the user wants to interact with Notion data.
Traditional development workflow skill for product requirement intake, engineering research, technical planning, task breakdown, implementation, testing, bugfix loop, and engineering review. Use when a user wants to run or continue a structured software delivery workflow that mirrors real product-development collaboration.
Implement Syncfusion WPF Gantt control for project management and task scheduling in Windows Presentation Foundation applications. Use this when building project planning tools, task timeline visualizations, or resource management systems. This skill covers Gantt chart configuration, task dependencies, drag-drop interactions, resource allocation, baseline tracking, and customization options.
Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.
Break requirements into epics and user stories. Use when the user says "create the epics and stories list"
Create subtasks in Jira from a previously generated task plan. Reads the plan from docs/<TICKET_KEY>-tasks.md and creates one Jira subtask per task under the parent ticket. Use when the user says "create subtasks", "push tasks to Jira", "sync plan to Jira", "create Jira tickets", "make subtasks for PROJECT-1234", or anything about turning a plan into Jira issues. Also triggered by the orchestrating-jira-workflow skill as Phase 4. Requires the task plan to already exist (run planning-jira-tasks first if it does not). Use this skill even if the user just says "push to Jira" or "create the tickets" after a planning phase — those are subtask creation requests.
Basecamp integration. Manage Projects, Persons, Clients. Use when the user wants to interact with Basecamp data.
Use when an approved epic is ready for implementation and the next current-phase bead should be executed directly in single-worker mode or by a single worker inside a swarm. Use for prompts like "implement this bead", "do the work", "run the worker", "start implementing", "execute the next task", or whenever approved current-phase work needs to move from plan into verified implementation one task at a time.
Use after PR hardening is complete, to sync knowledge across global documents and prepare the next phase
Use when you have an approved implementation plan document and need to execute it step by step. Triggers on /execute command, when transitioning from planning with an approved plan, or when resuming execution of a partially completed plan. Provides batch-based execution with TDD, checkpoint reviews, and verification gates.