Markdown Editor
Editor öffnen

Kit kleines Softwareteam

Schlanke Dokumente für kleine Teams: PRD, schlanke SRS, Design-Doc, ADR, RFC, Spike, Standards, Commits, PRs, Tests und Release.

14 Vorlagen in 5 Schritten, in der Reihenfolge der Nutzung. Öffnen Sie eine Vorlage im Editor, füllen Sie sie aus und exportieren Sie sie als PDF, DOCX oder HTML.

Schritt 1

Planung

  1. Product Requirements Document (PRD) Template

    Vollständig

    Lean path or full PRD: evidence, metrics with baseline and guardrails, non-goals, user flow, FR table with acceptance criteria, UX states, NFRs, privacy, events, rollout gates

    ISO/IEC 25010:2023 (NFR categories, cited); WCAG 2.2

  2. Lightweight SRS Template for Small Teams

    Standard

    Lightweight SRS for one small team, aligned with ISO/IEC/IEEE 29148:2018: scope, users, functional, non-functional and interface requirements, verification

    ISO/IEC/IEEE 29148:2018 (light); replaces IEEE 830

  3. Spike Report Template

    Kompakt

    Time-boxed technical investigation: question, success criteria, approach, findings with evidence, risks, recommendation and next steps

Schritt 2

Entscheidungen

  1. Software Design Document Template

    Standard

    Lean feature design doc: context, goals and non-goals, design, API and data changes, alternatives, cross-cutting concerns, rollout

  2. Architecture Decision Record (ADR) Template

    Standard

    Lightweight Nygard-style ADR: status, context, decision, consequences, alternatives, related decisions, lifecycle and log

    Michael Nygard ADR format (2011)

  3. RFC Template (Request for Comments)

    Standard

    RFC proposal: summary, motivation, guide-level explanation, detailed design, drawbacks, alternatives, prior art, rollout, decision

    Rust RFC process (section structure)
Schritt 3

Umsetzung

  1. Coding Standards Template

    Standard

    Team coding standards: naming, tool-enforced formatting, structure, errors, logging, tests, reviews, language rules

  2. Branching Strategy Template (Trunk-Based, SLSA Source)

    Vollständig

    Branching standard: model selection, naming, MUST/SHOULD rules, ruleset settings, SLSA Source mapping, merging, release branches, hotfixes, exceptions, metrics

    SLSA 1.2 Source track; DORA trunk-based development; Conventional Commits 1.0.0

  3. Commit Message Convention Template

    Standard

    Commit message standard: Conventional Commits structure, types and SemVer effect, scopes, breaking changes, footers and trailers, examples, commitlint and release tooling

    Conventional Commits 1.0.0; SemVer 2.0.0

  4. Pull Request Description Template

    Kompakt

    PR description: summary with closing keyword, type of change, breaking changes and migration, test plan, security, AI assistance disclosure

    GitHub pull request templates; Conventional Commits 1.0.0; SemVer 2.0.0; DCO 1.1
Schritt 4

Verifikation

  1. Test Plan Template

    Standard

    Practical feature or release test plan: scope, risks, approach per level, cases, environments, entry/exit criteria

  2. Code Review Checklist Template

    Standard

    Team code review agreement: review types (ISO/IEC 20246, IEEE 1028), roles, checklist with OWASP Top 10:2025 mapping and AI-assisted code items, labels, PR size, SLA

    ISO/IEC 20246:2017; IEEE 1028-2008; OWASP Top 10:2025
Schritt 5

Release und Übergabe

  1. Software Release Checklist Template (Staged Rollout, SBOM, VEX)

    Vollständig

    Per-release checklist: planning and pre-mortem, freeze, QA, security, 2026 SBOM fields, VEX and advisories, signing, ring rollout, emergency rollback, sign-offs

    CISA Safe Software Deployment (2024); CISA 2026 SBOM Minimum Elements; NIST SSDF 1.1

  2. Changelog Template (Keep a Changelog)

    Standard

    CHANGELOG.md in Keep a Changelog 1.1.0 format: Unreleased, six change types, YANKED, comparison links, maintainers' guide with SemVer 2.0.0 mapping

    Keep a Changelog 1.1.0; Semantic Versioning 2.0.0