Loading...
Loading...
Found 443 Skills
Asana integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Asana data.
Manage tasks using the fine CLI. Use this skill whenever the user asks to create, view, update, or work with tasks, project requirements, feature specs, or work tracking through markdown files. Also use it when the user mentions "fine" in the context of project management, or asks about task status, step progress, or wants to break work into tracked steps.
Github Issue Creator - Auto-activating skill for Enterprise Workflows. Triggers on: github issue creator, github issue creator Part of the Enterprise Workflows skill category.
MeisterTask integration. Manage Projects, Users, Roles. Use when the user wants to interact with MeisterTask data.
Get a recap from One Horizon across completed, planned, and blocked tasks, with initiatives and open bug/feature sections. Supports personal and team scope. Use for "my recap", "team recap", "team status", "what have I done and what's next", or "what is everyone working on". Requires One Horizon MCP.
Uncontrollable software development costs? We provide software cost estimation dashboard functionality.
Teamwork integration. Manage Organizations, Users. Use when the user wants to interact with Teamwork data.
When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.
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.
Top-tier software architect agent for complex multi-stage project development. This skill embodies the role of a senior software architect who decomposes complex tasks into structured sub-modules, iterates each component until excellence is achieved, enforces strict quality gates between phases, and produces documentation compliant with all skill standards. Core Philosophy: "Design once, iterate until perfect, then move forward." Triggers when: You need to design architecture for a complex multi-stage project, decompose requirements into modules, or establish quality gates for development phases. Commands: - /architect design <task> - Full architecture design for a task - /architect phase <n> - Execute specific phase - /architect iterate <module> - Iterate on a specific module - /architect status - Show current architecture status - /architect review - Review and validate architecture Six phases: Requirement Analysis, Architecture Design, Task Decomposition, Iterative Development, Integration & Validation, Documentation Generation. Each phase has strict exit criteria.
Backlog integration. Manage Projects. Use when the user wants to interact with Backlog data.
Stress-test a plan or design through structured interviewing. Use when the user wants to pressure-test a plan, resolve design decisions, or mentions "grill me".