All authors
Claude Skills by ChenxingJi-Innovate
github.com/ChenxingJi-Innovate9 skills0 installs0 views
- Comment RepliesDraft 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 comment is right, and lists the comments only the author can answer. Use when a doc has accumulated r...Votes: 0GitHub stars: 5
- Release Notes House VoiceWrite 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 "what's new" post or an internal release summary.Votes: 0GitHub stars: 5
- Fintech Spec SectionWrite 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, and the questions for compliance and the bank or sponsor partner. Use when specifying payments, len...Votes: 0GitHub stars: 5
- Healthcare Spec SectionWrite 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 clinical decisions and need a clinical safety or software-as-a-medical-device review, and the ques...Votes: 0GitHub stars: 5
- Acceptance CriteriaWrite 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.Votes: 0GitHub stars: 5
- Brd DraftDraft 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 elicitation material into a first draft for review, or when restructuring a messy requirements document.Votes: 0GitHub stars: 5
- Requirements LintReview 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, or when asked to "review", "check", "lint" or "tighten" requirements. Produces a findings table wit...Votes: 0GitHub stars: 5
- Traceability MatrixBuild 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, or when scope changes and the team needs to see what is affected.Votes: 0GitHub stars: 5
- Uat PlanPlan 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 when asked for a UAT plan, test scripts or a sign-off template.Votes: 0GitHub stars: 5