Cheatcode_

In the author's own words, from each skill's SKILL.md.

• comment-replies

  Draft replies to open comments on a spec, PRD or design doc (Confluence, Notion, Google Docs, or pasted) and to coworker questions, grounded in the document itself, linked decisions and prior threads, and staged for the author's approval. Classifies each comment (question, objection, suggestion, decision needed, out of scope), drafts a reply in the author's voice, proposes doc edits where the com…

  packages/pm-comms-kit/skills/comment-replies/SKILL.md on GitHub (opens in a new tab)

• release-notes-house-voice

  Write customer-facing release notes from commits, merged pull requests, closed tickets or a changelog, in the voice of the team's own past release notes. Learns the house style from examples (structure, tone, what gets mentioned and what never does) before drafting, groups changes by what users notice, and flags anything it could not explain. Use when preparing release notes, a changelog entry, a…

  packages/pm-comms-kit/skills/release-notes-house-voice/SKILL.md on GitHub (opens in a new tab)

• fintech-spec-section

  Write the regulatory and risk section of a PRD, BRD or feature spec for a money-moving or financial product: which obligations the feature triggers (KYC and customer due diligence, AML monitoring and suspicious activity reporting, sanctions screening, PCI DSS scope, consumer disclosures, record keeping, privacy), the controls and audit events each requirement needs, failure and exception paths, a…

  packages/regulated-spec-sections/skills/fintech-spec-section/SKILL.md on GitHub (opens in a new tab)

• healthcare-spec-section

  Write the regulatory, privacy and safety section of a PRD, BRD or feature spec for a healthcare product: whether the feature handles protected health information, which HIPAA safeguards and business associate obligations apply, minimum necessary access, consent, audit trails, retention, de-identification for analytics, interoperability (HL7 or FHIR resources), whether the feature could influence…

  packages/regulated-spec-sections/skills/healthcare-spec-section/SKILL.md on GitHub (opens in a new tab)

• acceptance-criteria

  Write acceptance criteria for user stories or requirements as Gherkin scenarios (Given, When, Then) or EARS statements, including negative, boundary and permission cases, so that business users and testers agree on done before development starts. Use when a story or requirement needs acceptance criteria, when existing criteria are vague, or when preparing stories for refinement or UAT.

  packages/requirements-kit/skills/acceptance-criteria/SKILL.md on GitHub (opens in a new tab)

• brd-draft

  Draft a business requirements document (BRD) from workshop notes, interview transcripts, emails and existing documents: objectives, scope, stakeholders, current and future process, numbered SHALL requirements grouped by functional area, business rules, data and reporting needs, non-functional needs, assumptions, constraints, dependencies, risks, glossary and open questions. Use when turning elici…

  packages/requirements-kit/skills/brd-draft/SKILL.md on GitHub (opens in a new tab)

• requirements-lint

  Review a requirements document, BRD, FRD, spec or backlog of user stories for the defects reviewers catch in sign-off meetings: ambiguous or subjective wording, untestable statements, undefined terms, missing non-functional requirements, missing edge and error cases, conflicts and duplicates, and statements that bundle several requirements. Use before a spec goes to stakeholders or engineering, o…

  packages/requirements-kit/skills/requirements-lint/SKILL.md on GitHub (opens in a new tab)

• traceability-matrix

  Build or update a requirements traceability matrix (RTM) as a CSV or spreadsheet that links business objectives to requirements, user stories, design items, test cases and their status, and report the gaps: requirements with no test, tests with no requirement, objectives with no requirement, and changed requirements whose tests were not updated. Use when preparing for sign-off, UAT or an audit, o…

  packages/requirements-kit/skills/traceability-matrix/SKILL.md on GitHub (opens in a new tab)

• uat-plan

  Plan user acceptance testing and write business-facing UAT scripts from requirements or acceptance criteria: scope, roles, environments and data, entry and exit criteria, schedule, defect triage rules, the step-by-step scripts testers follow, and the sign-off record. Use when a release or project is approaching UAT, when business testers need scripts they can run without the delivery team, or whe…

  packages/requirements-kit/skills/uat-plan/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 84.1k stars · 2 skills
• awesome-claude-skillsby ComposioHQ A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows 77.2k stars
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 54.9k stars · 30 skills