Loading...
Loading...
Found 443 Skills
Zoho Projects integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho Projects data.
SonarCloud integration. Manage Projects. Use when the user wants to interact with SonarCloud data.
Use BEFORE coding any non-trivial change. Explores user intent, demand, tradeoffs, and approach. Produces a design doc in docs/design-docs/, not code. Required for LARGE tasks, optional for MEDIUM, skip for SMALL.
Analyze a GitHub issue and create a detailed technical specification
Full task lifecycle: create → assign → monitor → review → reject/complete. Use when asked to "add a feature", "fix a bug", "create a task", "加个功能", "修个 bug", or "/ak-task <description>".
You are **SeniorProjectManager**, a senior PM specialist who converts site specifications into actionable development tasks. You have persistent memory and learn from each project.
Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
Taskade integration. Manage data, records, and automate workflows. Use when the user wants to interact with Taskade data.
Pre-sprint brief that locks scope, the decision the sprint must unlock, team and role assignments, logistics, inputs to bring, and success criteria before Day 1 of a Foundation Sprint. Use after the readiness verdict is Go and before the sprint begins. Produces a one-page artifact the team and Decider sign off on as the contract for the next two days.
To do / In progress / In review / Done 四列, 卡片 + 头像 + 泳道
Use when an academic research repository task could involve research design, sources, conversion, bibliography, SOTA, reviews, ethics, experiments, papers, reproduction, MCP tools, or project maintenance and the correct workflow is not obvious.
Mandatory only on the task-file path of `spec-loop-plan-task` after implementation approval. Use when implementation deviates from the approved task, when uncertainty must be clarified instead of guessed through, when new blocking questions arise, or before presenting the current task or subtask to the User. Governs clarification routing, canonical task updates when explicit User clarification, accepted review feedback, or explicit post-implementation User approval changes the current task definition, the post-implementation `Implementation notes` check, and whether the increment may move to `review`. May be applied in parallel with other implementation-related skills.