'prd' 검색 결과

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks which PRDs exist — 'listar PRDs', 'quais PRDs temos', 'list PRDs' — with status, version, roadmap state and GitHub Project. Read-only.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설계서나 요구사항에서 처음부터 끝까지 작동하는 작은 기능을 계획합니다. 초기 구조 생성, 생성과 평가 반복, 검토와 승인을 거쳐 최소 기능 제품을 만듭니다.

• 설계서에서 작동하는 MVP 구축
• 전체 흐름이 작동하는 작은 기능 계획
• 첫 기능의 초기 구조 생성

Turn a product requirements document for a major development initiative into a technical architecture specification, including a Mermaid system diagram, major features, supporting technologies, technical value, and a rough size estimate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning product requirements into a technical architecture
• Visualizing system layers and data flows
• Identifying services and infrastructure needed for features

Prioritize product features, analyze customer interviews, and draft product requirements documents. Scoring scripts and document templates help turn customer problems, expected impact, and development effort into a roadmap with clear scope and success measures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing features within team capacity
• Extracting customer problems from interviews
• Drafting requirements for a new feature

Turn a feature idea or user problem into a structured specification or product requirements document. Define goals, scope, priorities, success measures, and acceptance criteria, with phased delivery when the request is too large.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn a vague idea into a feature specification
• Define feature scope and priorities
• Set success measures and acceptance criteria

Turn existing decision records, product requirements, specifications, and other documents into GSD planning files. Create a new planning setup or add requirements and phases to an existing one, while identifying conflicts and blocking writes when contradictions remain unresolved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build planning files from existing project documents
• Add documented requirements and phases to an existing plan
• Identify conflicting statements across planning documents

Review a product launch against the team's legal framework and risk standards. Produce a category-by-category memo with required actions, owners, and deadlines, plus a separate tracker comment that omits internal legal reasoning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing legal issues before a product launch
• Listing required actions, owners, and deadlines
• Checking privacy and AI issues in a new feature

Organize product requirements into a single-page document covering the problem, success metrics, scope, user scenarios, design notes, rollout plans, and open questions. A status label shows whether the specification is a draft, approved, or shipped.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting requirements for a new product feature
• Defining success metrics and scope
• Documenting user scenarios and design notes

Run a YAML workflow, a file defining tasks and roles, using the AI in the current session. Resolve inputs and step dependencies, carry out each role's work, and save individual outputs and the final result.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running a workflow defined in a YAML file
• Reviewing a PRD with product manager and architect roles
• Creating a story with narratologist and psychologist roles

Coauthor proposals, specifications, and other structured documents through context gathering, section-by-section drafting, and revision. Test the finished draft with a fresh Claude conversation to identify unclear assumptions, missing information, and contradictions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning background notes into a proposal
• Drafting a technical specification or PRD
• Documenting a decision and its rationale

Turn the current conversation context into a PRD and publish it as a GitHub issue that is ready to receive sub-issues from /to-issues-project. Project-local variant of /to-prd, adapted for this repo's PRD-as-parent-issue + sub-issues + agent:implement workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues + agent:implement multi-session workflow. Argument is the parent PRD issue number.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The Atlas engine — turn any goal into a validated PRD and an executable, verified task graph. Brand-name entrypoint; a thin alias for the `go` orchestrator. Use when the user types /prd:atlas, says "I want to build", or asks for a PRD / task-driven build.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PRD・要件定義書・要求資料・レビューの生成に使用。 「PRDを作って」「要件定義書を書いて」「レビューして」「議事録を分析して」等のリクエストで発動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PRD（プロダクト要件定義書）の作成、機能仕様の策定、受け入れ基準の定義を行うスキル。 「PRDを書いて」「機能仕様を作って」「要件定義して」等のリクエストで発動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates Product Requirements Documents (PRD) for new features. Use when planning features or starting projects. Triggers on: create prd, write prd, plan feature, requirements, spec out.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem statement", "start v0.1", "what problem are we solving". Outputs structured problem tables with CFD evidence IDs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a lean, mobile-aware Product Requirements Document for a NowStack Mobile app through interactive discovery, then save it to .agents/plan/PRD.md. Use for "write a PRD", "ns prd", "define the product", "plan my app", or as the first planning step before ns-architecture and ns-tasks. Mobile-flavored — personas, onboarding/paywall flow, platforms (iOS/Android/web), IAP vs subscription monetization, store scope. Feeds ns-init-project (site-config) and the rest of the planning pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.