본문으로 건너뛰기
cccskills
무료GitHub에 공개

prd-writer

Turn a feature idea or rough notes into a product requirements document, or PRD. It organizes the problem, users, scope, prioritized requirements, success measures, and unresolved questions so a team can agree on what to build.

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

원문원문 설명 보기

Turn a feature idea into a clear PRD — problem, users, requirements, and success metrics.

holaboss-ai/holaOS
설치 방법 보기

이럴 때 유용합니다

  • Turn a feature idea into a product requirements document
  • Agree on goals and boundaries before development
  • Prioritize requirements and define success measures
  • Surface risks and unanswered questions

포함된 파일(1)

  • SKILL.md2.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Product Spec

Write the spec that gets a team building the right thing. A good PRD isn't a feature list — it's a shared understanding of the problem, who has it, what "done" means, and how you'll know it worked. It closes the gaps where projects usually go sideways.

When to use this skill

Use Product Spec to turn a feature idea, request, or rough notes into a product requirements document (PRD) or one-pager. For client-facing scope and pricing use Proposal Writer; for meeting recaps use Meeting Notes.

What a PRD needs to answer

  • Problem — what user pain or business need this addresses, and why now. If you can't state the problem, the feature isn't ready.
  • Users & context — who it's for and the situation they're in when they hit this.
  • Goals & non-goals — what this explicitly will and won't do. Non-goals prevent scope creep as much as goals drive it.
  • Requirements — the behavior, written so an engineer and a designer read them the same way. Separate must-haves from nice-to-haves.
  • Success metrics — how you'll measure whether it worked.
  • Open questions & risks — the unknowns, surfaced rather than buried.

Principles

  • Problem before solution. Anchor on the user's pain; a solution with no stated problem is a guess.
  • Unambiguous requirements. If a requirement can be read two ways, pick one and make it explicit.
  • Right altitude. Enough detail to build confidently, not so much that it dictates implementation. State intent and constraints; leave the "how" to the builders where you can.
  • Name the unknowns. List open questions instead of pretending certainty.

How to work

  1. Pin down the problem and the user before anything else.
  2. Set goals and non-goals; they bound everything after.
  3. Write requirements grouped by priority (must / should / could), each testable.
  4. Add success metrics, then list risks and open questions honestly.

Output format

A structured doc: Summary, Problem, Users & Context, Goals / Non-goals, Requirements (prioritized), Success Metrics, Risks & Open Questions. Keep it as short as the problem allows.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

app-builder-sdk

무료

Build holaOS apps for connecting external services or managing work through a dashboard. The skill uses shared SDK building blocks for stored records, actions, and synchronization, with the dashboard and agent tools working on the same data.

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

  • Building an external service integration
  • Creating a CRM dashboard
  • Building a content planning workspace
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

audience-analyst

무료

Analyze audience demographics and engagement to identify distinct groups, understand what they want, and prioritize valuable segments. Turn those findings into recommendations for content topics, formats, posting times, and tone, while explaining limits in the data.

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

  • Identify distinct groups within an audience
  • Prioritize groups that engage or convert
  • Plan topics and formats for each audience group
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

browser-core-efficient

무료

Guide an agent through efficient use of an embedded browser by choosing targeted actions, searches, and waits. Reduce repeated tool calls and unnecessary page snapshots, while using more detailed inspection when the target or result remains unclear.

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

  • Act on known buttons or fields with fewer browser calls
  • Locate a known target on a large page
  • Wait for navigation or downloads to finish
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

browser-qa

무료

Validate workflows and reproduce issues in an embedded browser. Distinguish application problems from incorrect targets, missing waits, or session state, then report the shortest reliable reproduction steps with only the evidence needed to support the finding.

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

  • Reproducing a browser workflow failure
  • Checking for regressions after a fix
  • Distinguishing timing issues from application failures
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

build-dashboard

무료

Build the user interface for a holaOS app whose data resources are already connected through the SDK. Choose a feed, table, kanban board, form, or calendar layout using shared components and workspace styling.

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

  • Display scheduled items in a chronological feed
  • Show CRM contacts or tickets in a table
  • Organize issues by status on a kanban board
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

capability-creator

무료

Package workspace skills and their required service integrations into one named, installable capability. Create a manifest that references existing skills, install the capability, and report which integrations still need to be connected.

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

  • Bundle multiple skills for a shared outcome
  • Declare required external service integrations
  • Create a manifest that references existing skills
holaboss-ai/holaOS1.1만2026년 8월 21일 업데이트

holaboss-ai의 스킬 모두 보기

이 스킬의 문제 신고