Loading...
Loading...
Found 314 Skills
Estrategista de produto no SynkOS. Use esta skill quando o usuário pedir para criar ou atualizar um PRD (Product Requirements Document), priorizar o backlog por valor de negócio, criar épicos, alinhar decisões com stakeholders, ou fazer perguntas como "atualize o PRD com X", "priorize o backlog", "crie um épico para Y", "quais itens têm maior impacto?", "como comunicar esse tradeoff ao cliente?", "o backlog está alinhado com os objetivos de produto?". Ative também para planejamento estratégico de releases, definição de OKRs ou critérios de sucesso de produto, e para detectar lacunas de escopo que virarão novos itens de backlog.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
Use when creating a PRD, writing requirements, or transforming a feature request into an implementation-ready GitHub issue.
Analyze HM Desktop PRD documents, extract requirement information, verify completeness, check chapter order (Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description), inspect KEP definitions, detect requirement conflicts, and generate structured analysis reports. Applicable to user requests: (1) Analyze or review PRD documents, (2) Extract KEP lists from requirements, (3) Check PRD completeness or consistency, (4) Map requirements to module architecture, (5) Verify PRD format compliance, (6) Verify completeness of competitor analysis chapters. Keywords: PRD analysis, requirement extraction, KEP verification, completeness check, chapter order validation, competitor analysis check, analyze PRD, requirement extraction, completeness check, chapter order validation
New Feature Design Exploration Process. Used when users have vague ideas for new features or modules. Through the structured process of "Requirements Convergence → Technical Research → ASCII Batch Exploration → HTML Design Draft → Full State Coverage → Requirements Summary", deliverable design reference documents are generated from vague ideas, serving as input for the PRD phase.
Product requirements → living doc Requirements section + quality gate + domain glossary. Stateful: detects existing sections and resumes where needed. Triggers: 'define this,' 'write a PRD,' 'define requirements,' 'spec this out,' post-explore. Not for: scoping (explore), UX (design), technical design (architect).
Synthesize a PRD (Product Requirements Document) for a big new feature. Synthesis (not interview) — uses existing project context and explicit ADRs. Asks before gh issue create. Use when scoping a substantial new feature in PRD shape (e.g., before a sprint).
[Hyper] Create or update a ManyFast-style AI planning package from a rough product idea: PRD, visual planning diagram, feature spec, user flow, low-fidelity wireframe, HTML preview viewer, source log, and optional flow tracking under `.hypercore/prd/[slug]/`. Use when the user wants product planning output before implementation, especially PRD plus diagram/specs/flows/wireframes.
Runs an autonomous delivery loop from an existing PRD to implementation, issue triage, per-slice verification, and final repo validation. Use when the user has already created or approved a PRD and asks to automate to-issues, tickets, triage, ready-for-agent implementation, validation, or production-ready completion.
Use when the user asks to create a feature, write a PRD or TRD, add user stories, write scenarios, create acceptance criteria, plan implementation, initialize product docs, set up product documentation, create, approve, amend, or validate a Product Constitution, run the Constitution Grill, create or maintain Product Vision, run a Vision Grill, or work anywhere in the product development lifecycle from project setup through implementation planning.
Implement a piece of work based on PRD or a collection of issues.
Guides PRD, ADR, Design Doc, and Work Plan creation with templates and decision matrix.