Discover blockchain sales marketing skills, compare source repositories and read the instructions for each workflow.
Generate a Product Requirements Document (PRD) for loopwright task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a...
Interactive daily productivity review with guided priority setting. Supports morning planning, midday check-ins, and end-of-day wrap-ups. Use for daily ritual or cron automation.
Create detailed implementation plans with granular, actionable tasks (2-5 min each). Use for multi-step development tasks requiring clear guidance. Based on obra/superpowers.
Reviews in-progress implementation against feature specification and plan - provides structured compliance report with categorized issues for fixing. Mid-implementation checkpoint for quality.
Proactively use when planning a complex multi-step implementation.
Reviews existing specifications for ambiguity and missing decision points - uses structured taxonomy to detect gaps, generates prioritized clarification questions, reduces specification uncertainty.
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and increm...
Develop, refine, and maintain project constitutional principles - uses Socratic questioning to eliminate ambiguity and ensure perfect clarity on design values and non-negotiables
Use when creating technical specifications for features, systems, or architectural designs. Creates comprehensive specification documents using the Wrangler MCP issue management system with proper structure and...
This skill should be used when the user asks to "define requirements", "create specification", "clarify requirements", "write requirements document", or mentions requirement analysis. Provides comprehensive req...
Collaborative design refinement through iterative questioning. Use for transforming ideas into detailed specifications before implementation. Based on obra/superpowers.
Competitive intelligence with positioning analysis, battlecards, and market monitoring. Use for competitor tracking, differentiation strategy, and win/loss analysis. Based on alirezarezvani/claude-skills.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
合并需求问题答案，生成完备需求
识别需求文档中的问题
Orchestrate Jira workflows end-to-end. Use when building stories with approvals, transitioning items through lifecycle states, or syncing task completion with Jira.
Professional internal communications creation and management with templates for status reports, newsletters, announcements, team updates, and cross-functional communication. Use for: (1) Weekly/monthly status r...
Complete REST API development workflow coordinating backend, database, testing, documentation, and DevOps agents. 2-week timeline with TDD approach.
Creates detailed handoff documents for the current session. Use when the user wants to document session progress for work continuation, says 'handoff', 'summarize session', 'create handoff', or is ending a work...
Proactive token budget management tool for assessing usage, analyzing task complexity, generating chunking strategies, and creating execution plans that stay within budget limits
Query and manage Linear issues, projects, and team workflows.
Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.
Use Claude Code's interactive question tool to gather comprehensive requirements through structured multi-select questions
This skill should be used when the user asks to "understand customers", "customer research", "user personas", "customer needs analysis", "buyer journey mapping", "voice of customer", "customer segmentation", "u...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.