Loading...
Loading...
Found 18 Skills
Use when an agent reports a discovered task via Nexus, to review, approve as official task, reject, or escalate to idea
GitLab search operations via API. ALWAYS use this skill when user wants to: (1) search across GitLab globally, (2) find issues/MRs/code/commits, (3) search within a group or project, (4) find users or projects by keyword.
Find or sharpen the project idea and write the scope doc. The first and most important planning conversation — a focused flipped-interaction interview that pulls the idea out of the learner's head, then cuts it down to a coherent proof of concept. Run after 1-start.
Routes project-level vs application-scoped work; avoids creating or selecting an application for simple website/function-only tasks unless needed.
Expert in protecting projects from scope creep. Covers requirement management, stakeholder negotiation, saying no diplomatically, and keeping projects focused. Understands that scope creep kills more projects than technical debt. Use when "scope creep, feature request, can we also, while you're at it, one more thing, requirements changed, scope management, " mentioned.
This skill should be used when the user asks to "stop scope creep", "limit revision rounds", "write SOW revision language", "the client keeps asking for changes", "how do I say this is out of scope", "translate vague feedback", "client said make it pop", or "write a change-order email". It provides revision-cap contract language, a consolidated-feedback request, a vague-feedback translator, and a polite out-of-scope email.