메뉴
이 저장소의 skills
SkillsMP는 peterbamuhigire/srs-skills에서 158개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
peterbamuhigire/srs-skills수집된 skill 158개 중 38개를 표시합니다.
Use when documenting verified prerequisites, installation, configuration, validation, upgrade, and uninstall procedures. Use user-manual for post-install operation and release-notes for version-specific migration changes.
원문 언어: 영어
Use when converting recurring, evidence-backed user questions into concise searchable answers with documentation links. Use user-manual for complete procedures and installation-guide for setup sequences.
원문 언어: 영어
Use when communicating a verified version delta, including features, fixes, breaking changes, migration steps, compatibility, and known issues. Use user-manual for durable product operation and baseline-delta for controlled document changes.
원문 언어: 영어
Use when defining SaaS health scoring, lifecycle intervention plays, QBRs, dunning recovery, escalation, renewal, and expansion operations. Use onboarding-journey-spec for activation design and lifecycle-email-strategy-doc for email execution.
원문 언어: 영어
Use when defining consent-aware SaaS acquisition, activation, adoption, retention, expansion, risk, and win-back email campaigns with triggers, suppression, QA, and measurement. Use onboarding-journey-spec for in-product activation.
원문 언어: 영어
Use when producing product-specific ICP, discovery, demo, qualification, battlecard, and closing material for a sales-assisted SaaS. Use customer-success-playbook for post-sale operations and FAQ for customer self-service answers.
원문 언어: 영어
Use when preparing user-facing disclosures for an AI agent's capabilities, limits, data use, autonomy, approvals, escalation, and incident contact. Use responsible-ai-addendum for internal governance and DPA language for contractual processing terms.
원문 언어: 영어
Use when mapping requirements to designs, tests, evidence, releases, and approvals so gaps and orphan artefacts are visible. Use baseline-delta for version-to-version changes and evidence-pack-builder to package proof.
원문 언어: 영어
Use when producing a governed compliance document set from verified obligations, controls, owners, evidence, review cadence, and approvals. Use audit-report for independent findings and regulator-overlap-mapping for cross-regime reuse.
원문 언어: 영어
Use when identifying, analysing, treating, and accepting project or system risks with evidence-backed likelihood and impact. Use change-impact-analysis for a proposed change and audit-report for retrospective control findings.
원문 언어: 영어
Use when recording a consequential architecture choice, context, options, rationale, consequences, owner, and supersession path. Use ai-adr-catalogue for AI-system decisions and formal-review-gates for approval checkpoints.
원문 언어: 영어
Use when defining or operating evidence-based lifecycle review gates, entry criteria, decision rights, outcomes, and remediation. Use sign-off-ledger to record approvals and waiver-management for time-bound exceptions.
원문 언어: 영어
Use when establishing a Change Control Board's scope, membership, quorum, decision rights, evidence requirements, records, and escalation. Use change-impact-analysis for a specific change and sign-off-ledger for decisions.
원문 언어: 영어
Use when assessing a proposed change against baselines, requirements, architecture, security, privacy, tests, operations, schedule, and cost before authorisation. Use baseline-delta to record the approved delta and CCB-charter for governance.
원문 언어: 영어
Use when recording the exact approved differences between controlled baselines, including affected artefacts, rationale, evidence, migration, and rollback. Use change-impact-analysis before approval and release-notes for customer-facing changes.
원문 언어: 영어
Use when documenting, approving, monitoring, expiring, or closing a time-bound exception to a requirement or control. Use risk-assessment to evaluate exposure and sign-off-ledger to record the accountable decision.
원문 언어: 영어
Use when maintaining an immutable, attributable record of review, approval, rejection, conditions, scope, and date. Use formal-review-gates to define gate criteria and waiver-management for exceptions.
원문 언어: 영어
Use when assembling indexed, traceable, integrity-checked evidence for a review, audit, release, or acceptance decision. Use traceability-matrix to expose coverage and audit-report to assess the assembled evidence.
원문 언어: 영어
Use when proving tenant isolation across identity, application, database, storage, cache, queue, analytics, support, and backup boundaries. Use evidence-pack-builder for generic packaging and DPA/privacy-doc-set for processing obligations.
원문 언어: 영어
Use when preparing verified customer-facing security, privacy, availability, subprocessor, and compliance material for a SaaS trust centre. Use evidence-pack-builder for internal proof and DPA/privacy-doc-set for contractual privacy documents.
원문 언어: 영어
Use when drafting a SaaS privacy notice, DPA, processing schedule, subprocessor disclosure, retention terms, and data-subject procedures from verified flows and legal review. Use trust-center-document-pack for public assurance material.
원문 언어: 영어
Use when documenting an AI feature's intended use, limits, human oversight, evaluation, data, safety, fairness, transparency, and accountability. Use ai-data-flow-and-dpia for privacy risk and responsible-ai-addendum for agent-specific controls.
원문 언어: 영어
Use when classifying AI features against applicable regulatory regimes and mapping obligations, evidence, owners, gaps, and release conditions. Use regulator-overlap-mapping for multi-regime evidence reuse and responsible-ai-declaration for product disclosure.
원문 언어: 영어
Use when mapping AI data flows and assessing privacy necessity, lawful basis, risks, controls, residual risk, and consultation triggers. Use DPA/privacy-doc-set for contractual documents and responsible-ai-declaration for broader AI governance.
원문 언어: 영어
Use when maintaining a catalogue of consequential AI architecture, model, data, evaluation, safety, and provider decisions. Use architecture-decision-records for general ADRs and ai-agent-adr-catalogue for autonomous-agent decisions.
원문 언어: 영어
Use when extending a responsible-AI declaration with agent autonomy, action approval, supervision, kill switch, memory, auditability, and red-team controls. Use user-disclosure-pack for customer language and compliance-policy-pack for signed policies.
원문 언어: 영어
Use when recording agent-specific decisions about autonomy levels, planners, tools, approvals, memory, supervision, reversibility, and audit logs. Use ai-adr-catalogue for non-agent AI decisions and architecture-decision-records for general architecture.
원문 언어: 영어
Use when mapping an L1+ AI agent to SOC 2 trust-services controls, implementation evidence, sampling, testing, exceptions, and owners. Use ISO 27001 or HIPAA control packs for those frameworks and evidence-pack-spec for collection rules.
원문 언어: 영어
Use when mapping an L1+ AI agent to ISO/IEC 27001:2022 and applicable ISO/IEC 42001 controls, treatment, evidence, testing, sampling, and the SoA delta. Use SOC 2 or HIPAA packs for those regimes.
원문 언어: 영어
Use when mapping a PHI-touching AI agent to HIPAA Security Rule safeguards, minimum-necessary access, BAA duties, evidence, testing, and breach handling. Use ISO 27001 or SOC 2 packs for those frameworks.
원문 언어: 영어
Use when producing signed, auditor-readable policies for agent actions, audit logs, approval, supervision, kill switch, memory erasure, red-team work, evidence, and attestation. Use control packs for framework mappings and evidence-pack-spec for proof.
원문 언어: 영어
Use when planning evidence collection, remediation, rehearsals, and audit-day execution for an AI-agent SOC 2 Type II, ISO 27001 surveillance, or HIPAA review. Use control packs to define controls and evidence-pack-spec to define evidence handling.
원문 언어: 영어
Use when defining AI-agent compliance evidence items, sources, collection, sampling, integrity, chain of custody, retention, redaction, presentation, and auditor access. Use evidence-pack-builder to assemble a specific pack and control packs to define…
원문 언어: 영어
Use when drafting legal-review-ready AI-agent BAA or DPA addendum clauses for service-principal access, audit logs, kill switch, memory, subprocessors, training exclusion, breach, and transfers. Use HIPAA control pack for controls and privacy-doc-set for the…
원문 언어: 영어
Use when crosswalking AI-agent controls and evidence across two or more regulatory or assurance regimes while exposing divergent obligations. Use each regime's control pack for authoritative detail and evidence-pack-spec for handling requirements.
원문 언어: 영어
Use when producing any SRS, requirement, design, test, ADR, document, or code artefact; apply continuously and at the pre-ship gate to prevent generic, unverified, template-shaped output. Use 29-ai-slop-audit for independent detection and grading.
원문 언어: 영어
Use when independently reviewing a concrete artefact for AI slop after a major iteration, on an audit or critique request, or before release. Produce evidence-backed findings and a grade; use 28-anti-ai-slop during production to prevent defects.
원문 언어: 영어
Use when creating the named SDLC artefact; use the nearest phase neighbour when it owns a different decision or deliverable.
원문 언어: 영어