Loading...
Loading...
Found 43 Skills
Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption.
Implement PRDs/specs with a mandatory precheck review before coding. Use when a user asks to implement a PRD/feature spec/requirements doc or says "implement PRD/spec". Perform a preflight review, raise questions on scope/consistency/risks, then implement after confirmation.
Navigate open source product strategy, community dynamics, and sustainable maintenance. Use when planning OSS releases, managing contributors, handling community expectations, balancing commercial and community interests, or when the user needs battle-tested wisdom on building in the open.
Manage stakeholder expectations and engagement through targeted communication, regular updates, and relationship building. Tailor messaging for different stakeholder groups and priorities.
Create and manage structured meeting notes with automatic action item extraction and governance integration. Use when user mentions "meeting notes", "record meeting", "create meeting", "standup", "retrospective", "planning", or any meeting-related keywords.
Devil's advocate. Seek contrary evidence before locking in. Use when about to make a significant decision, when confidence is high but stakes are higher, or when the team is converging too quickly.
Conduct stakeholder analysis using identification, Power-Interest matrix classification, and influence strategy development. Use this skill when the user needs to map stakeholders for a project, manage conflicting interests, prioritize communication, or build a stakeholder engagement plan — even if they say 'who needs to approve this', 'how do I get buy-in', or 'who might block this project'.
Use when you have confirmed the scope of Discover (P0/P1/P2), and now need to quickly build the Level-0 North Star (memory) and Level-1 map layer index skeleton (components/products) under `.aisdlc/project/`, so that you can supplement evidence by module later without double writing and drift.
Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.
Phase 1 of the Issue Workflow - Translate the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Phase 2's responsibility). This phase is also the only official decision point for determining whether to take the fast track or the standard path: first read the relevant code based on the user's description, and if the root cause can be identified at a glance and the changes required are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "log this bug", "I found a problem". This is the starting point of the issue workflow with no pre-requisites.
Use when you find additional work needed during task execution that's not in the original task description, to report it to ZŌE for review
Use to coordinate approvals, communications, and accountability across teams for feedback programs.