Menü
SkillsMP hat 158 Skills aus peterbamuhigire/srs-skills gesammelt. Öffne einen Skill, um Quelle und Details zu prüfen.
Es werden 40 von 158 gesammelten Skills angezeigt.
Use when independently reviewing drafted requirements for correctness, completeness, consistency, feasibility, traceability, and testability before baselining; use requirements-analysis to resolve raw elicitation conflicts.
Quellsprache: Englisch
Use when comparing solution candidates or prototypes to reduce uncertainty before locking requirements or design; use UX-specification after the chosen interaction direction is approved.
Quellsprache: Englisch
Use when specifying a SaaS aha event, activation milestones, segmented paths, nudges, measurement sources, and drop-off interventions. Use customer-success-playbook for ongoing intervention and user-manual for product procedures.
Quellsprache: Englisch
Use when specifying, planning, tracing, or reviewing realistic synthetic SaaS demo data and application-workflow test coverage for an SRS, PRD, test plan, release gate, or go-live evidence pack.
Quellsprache: Englisch
Use when auditing or improving the SDLC documentation engine or any PRD, SRS, architecture, test, deployment, governance, or game documentation product it produces.
Quellsprache: Englisch
Use when converting approved discovery evidence into a traceable PRD with objectives, prioritised features, success measures, constraints, and release scope; use vision-statement for the strategic north star and lean-canvas while assumptions still need…
Quellsprache: Englisch
Use when a SaaS or digital product needs to choose, tier and sequence AI features, separate table stakes from differentiation, decide build versus buy, and define an AI moat; use AI economic value brief for a single initiative's value proof and AI…
Quellsprache: Englisch
Use when defining a game's player promise, product hypotheses, platform options, production model, vertical-slice evidence, commercial boundaries, or greenlight decision before detailed requirements.
Quellsprache: Englisch
Use when converting an approved AI feature strategy into testable PRD requirements for quality, latency, cost, abstention, citations, consent, and evaluation; use ai-feature-strategy-doc for portfolio choices.
Quellsprache: Englisch
Use when specifying testable game software requirements for player experience, gameplay state, platforms, multiplayer, saves, content, performance, accessibility, telemetry, security, builds, release, or live operations.
Quellsprache: Englisch
Use when approved AI features need architecture decisions for direct calls, RAG, fine-tuning or agents, plus model gateway, knowledge stores, evaluation, observability and tenant security; use HLD for the whole system and agent architecture for tool-using…
Quellsprache: Englisch
Use when designing game client, authoritative state, engine integration, content, saves, multiplayer backend, platform adapters, telemetry, security, build, and live-operations architecture from an approved game SRS.
Quellsprache: Englisch
Use when specifying a reusable AI feature evaluation harness with datasets, graders, thresholds, calibration, regression gates, and run evidence; use ai-agent-eval-spec for multi-step tool-using agent evaluation.
Quellsprache: Englisch
Use when planning game QA, playtesting, balance, deterministic simulation, save migration, multiplayer network conditions, device performance, accessibility, localisation, security, certification, and release-candidate evidence.
Quellsprache: Englisch
Use when rolling out a non-agentic AI feature through offline, shadow, limited, and wider exposure with evaluation gates, bake periods, rollback triggers, and owners; use ai-agent-rollout-runbook for autonomy changes.
Quellsprache: Englisch
Use when facilitating a sprint retrospective that turns evidence into owned, time-bound improvement actions. Use sprint-planning for forward commitment and audit-report for an independent compliance review.
Quellsprache: Englisch
Use when independently assessing controls or delivery evidence and issuing read-only findings, severity, scope limits, and corrective actions. Use risk-assessment for prospective risk analysis and compliance-documentation to author control artefacts.
Quellsprache: Englisch
Use when turning approved game requirements and architecture into implementable Unity, Godot, Unreal, Apple-native, multiplayer, content-pipeline, build, and telemetry work packages with code and asset contracts.
Quellsprache: Englisch
Use when documenting reproducible game builds, signing, artifact promotion, distribution, staged rollout, rollback, crash diagnosis, matchmaking operations, live events, remote config, economy controls, support, or incidents.
Quellsprache: Englisch
Use when assembling or reviewing game greenlight, milestone, release, rights, security, player-research, build, test, live-operations, and independent-replication evidence without inflating capability claims.
Quellsprache: Englisch
Use when specifying a game's 3D asset and Blender source-to-engine pipeline, including asset briefs, rigs, animation clips, UV/bakes, materials, LODs, collision, export/import, lineage, automation, runtime budgets, and acceptance evidence; use…
Quellsprache: Englisch
Use when decision-makers need a go/no-go business case with cost, benefit, risk, timing, assumptions, and sensitivity evidence; use vision-statement for direction, lean-canvas for early hypotheses, and PRD generation only after investment approval.
Quellsprache: Englisch
Use when a project needs a concise strategic north star defining target users, problem, differentiated value, success and scope boundaries; use lean-canvas to test uncertain assumptions and PRD generation to specify approved product behaviour.
Quellsprache: Englisch
Use when an MVP, startup, SaaS, AI, website or mobile initiative still has material customer, problem, channel or value assumptions to test through a Lean Canvas, Impact Map and Hypothesis Board; use PRD generation once evidence supports stable requirements.
Quellsprache: Englisch
Use when every stakeholder needs a plain-language, current view of system purpose, context, major functions, constraints and actors; use vision-statement for strategic intent, PRD generation for product requirements, and high-level-design for technical…
Quellsprache: Englisch
Use when an AI feature, agent, RAG workflow, predictive product or automation proposal needs business outcomes, data readiness, evaluation, operating cost, risk and delivery evidence before PRD or architecture work; use AI feature strategy for portfolio…
Quellsprache: Englisch
Use when a commercial product, client-facing system, SaaS, app or executive workflow must justify premium pricing through buyer trust, proof, service quality and materially better experience; use vision-statement for broad direction and UX specification for…
Quellsprache: Englisch
Use when an early-stage or new SaaS product line needs a tightly bounded v1, one acquisition channel, explicit cuts, escape-velocity measures and a feature-triage log; use lean-canvas while the customer problem is still untested and PRD generation for the…
Quellsprache: Englisch
Use when a SaaS product needs an evidence-based defensibility plan covering integrations, owned channels, switching costs, proprietary data, brand or network effects; use competitive discovery for market facts and MVP scoping for initial release boundaries.
Quellsprache: Englisch
Use when a SaaS product needs testable tiers, a value metric, feature gates, expansion mechanics, freemium decision, grandfathering and price-change policy; use business-case for investment viability and PRD generation for feature requirements.
Quellsprache: Englisch
Use when a product may ship tool-using AI agents and needs to decide agent versus workflow, autonomy levels, tiered capabilities, action-catalogue advantage and sequencing; use AI feature strategy for the wider AI portfolio and agent architecture after…
Quellsprache: Englisch
Use when specifying SaaS usage events, billing, credits, refunds, dunning, finance handoff, and testable metering controls; use pricing-and-packaging for commercial tier design.
Quellsprache: Englisch
Use when specifying AI knowledge sources, ingestion, tenant isolation, freshness, retention, lineage, and training-data exclusions; use ai-feature-prd-spec for user-facing behaviour.
Quellsprache: Englisch
Use when defining testable product requirements for an agent's task scope, autonomy, budgets, intervention, success, and irreversible-action gates; use ai-agent-strategy-doc for portfolio strategy.
Quellsprache: Englisch
Use when defining the schema-bound tools an AI agent may invoke, including side effects, reversibility, approvals, audit fields, quotas, and kill switches; use agent PRD for user outcomes.
Quellsprache: Englisch
Use when specifying software that touches money, inventory value, payroll, tax, grants, payments, assets, or financial reports; use the finance doctrine for accounting policy and current statutory facts.
Quellsprache: Englisch
Use when decomposing approved features into INVEST user stories, epics, story points, and initial acceptance criteria; use acceptance-criteria when stories already exist and only test oracles are needed.
Quellsprache: Englisch
Use when formalising deterministic Given-When-Then acceptance criteria for existing user stories; use user-story-generation when the backlog or personas have not yet been defined.
Quellsprache: Englisch
Use when arranging an existing backlog into user activities, a walking skeleton, and release slices; use backlog-prioritization for economic ordering after the map exists.
Quellsprache: Englisch
Use when ranking an approved backlog with MoSCoW and WSJF and assigning release or sprint order; use story-mapping when the user journey and walking skeleton are not yet visible.
Quellsprache: Englisch