visualizing-subagents
Visualize subagent task dependencies using ASCII diagrams before launching agents and create comprehensive HTML summaries after completion.
Discover tools sales marketing skills, compare source repositories and read the instructions for each workflow.
Visualize subagent task dependencies using ASCII diagrams before launching agents and create comprehensive HTML summaries after completion.
Complete PDF forms by collecting data through conversational interviews and populating form fields. Use when filling forms, completing documents, or when the user mentions PDFs, forms, form completion, or docum...
Create Product Requirements Documents (PRDs), Architecture Documents, Epics, and User Stories using the BMAD (Breakthrough Method for Agile AI Driven Development) methodology. Use when user requests PRDs, archi...
Establishes SDD methodology - workflow routing, process discipline, spec-first principle, and skill discovery. Use when starting any SDD conversation to determine which workflow skill to invoke.
Load relevant design documents and project context before working on any task. Use when user asks about features, requests implementation, discusses functionality, analyzes architecture, updates documentation,...
Technical writing best practices including documentation structure, clear writing principles, API documentation, tutorials, changelogs, and markdown formatting. Use when writing documentation, creating READMEs,...
Use when starting from rough ideas - refines concepts into executable specifications through collaborative questioning, alternative exploration, and incremental validation, use this skill when called from a com...
Create specifications directly from clear requirements - uses spec-kit tools to create formal, executable specs following WHAT/WHY principle (not HOW)
Display project status and backlog overview. Use when user asks about current status, what's in progress, what to work on next, or wants a summary of the backlog. Read-only skill that formats DASHBOARD.md into...
Check project backlog when discussing feature ideas or priorities. Use when user mentions adding features, asks what's planned, discusses priorities, or proposes new functionality. Silently reads DASHBOARD.md t...
Enrich creator profiles using Talent API data for better discovery and ranking.
Automated sprint planning and execution from technical specifications (prompt generation, dependency planning, stateful execution)
Manufacturing-fokussierter Continuous Improvement Skill fuer fabrikIQ. Implementiert Lean Manufacturing Prinzipien (5 Whys, Ishikawa, PDCA) fuer systematische Problemloesung und Qualitaetsverbesserung. Aktivier...
LinkedIn Content-Erstellung, Engagement und Monitoring für B2B/Manufacturing. Regionale Anpassung (US/EU/Asien), Artikel mit Teasern, Bildgenerierung via Gemini, Kommentar-Monitoring.
1-page Concept Definition document creation for product ideas
Persona document creation following working backwards methodology and customer obsession principles
(opencode-project - Skill) Template and guidelines for creating comprehensive requirements specifications
(opencode-project - Skill) Template and guidelines for breaking features into implementation tasks
Comprehensive frontend design principles for creating distinctive, aesthetically compelling web interfaces. Use when creating HTML artifacts, React components, or any frontend UI work to avoid generic "AI slop"...
Use for planning workflows: clarifying underspecified work, spec-driven delivery, and Linear-backed tracking.
Interview user with targeted questions to clarify requirements. Use this BEFORE starting any implementation when instructions are vague or lack detail.
Theme and branding patterns.
Patterns for advanced product pricing logic, rentability calculations, and reactive price management in Vendix. Trigger: When editing product schemas, pricing logic, or advanced product forms.
Extended reasoning analysis using sequential thinking. Use for deep exploration, comprehensive analysis, complex decisions, or when you need fresh perspectives on difficult problems.
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.