Loading...
Loading...
Found 19 Skills
Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
Transform vague product ideas into concrete, executable strategies with clear metrics, user impact, and technical feasibility.
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.
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
Unified prompt engineering and requirements planning. Use when exploring ideas, improving prompts, creating PRDs, generating task breakdowns, or iterating on existing plans. Includes Jira integration for creating subtasks from plans.
사용자의 업무 문제, 아이디어와 제공된 자료를 구현 가능한 제품 정의로 구체화한다. 아이디어가 없거나 일부 맥락만 있거나 명확한 아이디어가 있어도 사용자·업무·UX 정보의 부족을 단계적으로 확인한다. “무엇을 만들지 정리해줘”, “아이디어를 구체화해줘”, “요구사항 문서를 만들어줘”, “PRD를 만들어줘”처럼 구현 전에 사용자·문제·범위·완료 조건과 경험 방향을 정하는 요청에 사용한다. 제품 정의와 UX 방향이 이미 충분히 확정되어 코드 변경만 요청한 경우에는 사용하지 않는다.
Turn the current conversation into a spec (Problem, Solution, User Stories, Decisions) and publish it as a GitHub issue. Validates a feature before any code is written.