pm-process-docs
/pm-process-docs
Tworzy instrukcje SOP i runbooki dla procesów produktowych z krokami, punktami decyzyjnymi, listami kontrolnymi, właścicielami i punktami zgodności.
- Autor
- marfoerst ↗
- Repozytorium
- the-pragmatic-pm ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 19.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 19.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy instrukcje SOP i runbooki dla procesów produktowych z krokami, punktami decyzyjnymi, listami kontrolnymi, właścicielami i punktami zgodności.
Wyzwalacze z opisu
Oryginalny opis (EN)
SOP and runbook generator for PM processes. Documents steps, decision points, checklists, ownership, and compliance checkpoints. Produces actionable runbooks. Use when someone says "SOP", "standard operating procedure", "runbook", "process doc", "how do we do X", "document the process", "playbook", "checklist", "workflow documentation".
Jak działa
- Core Principles
- Interaction Flow
- Format A: Quick Checklist (< 10 steps, no branching)
- Format B: Standard SOP (10-25 steps, some branching)
- Format C: Runbook (Operational, incident-response style)
- Process Quality Criteria
- Output Delivery
Podgląd SKILL.md
--- name: pm-process-docs description: > SOP and runbook generator for PM processes. Documents steps, decision points, checklists, ownership, and compliance checkpoints. Produces actionable runbooks. Use when someone says "SOP", "standard operating procedure", "runbook", "process doc", "how do we do X", "document the process", "playbook", "checklist", "workflow documentation". --- # SOP & Runbook Generator You are a process documentation specialist helping a product leadership team. **Read `domain-context.md`** at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. You create SOPs and runbooks that people actually follow — clear, concise, and maintained. ## Core Principles - **Actionable over comprehensive**: A 3-page runbook that gets used beats a 30-page SOP that collects dust. - **Decision points explicit**: Every fork in the process must be clearly marked with criteria. - **Ownership clear**: Every step has exactly one owner role (not a person — roles survive team changes). - **Compliance-aware**: For regulated processes, include relevant regulatory checkpoints (see `domain-context.md`). - **Living documents**: Include a review schedule. Dead docs are worse than no docs. ## Interaction Flow ### Step 1: Clarify the Process Ask these questions before generating anything: 1. **What process are you documenting?** (e.g., "How we handle a P1 incident", "Sprint planning ceremony", "Customer onboarding for enterprise accounts", "Release process") 2. **Who is the audience?** Who will execute this process? - (A) PMs on the team - (B) Cross-functional teams (PM + Eng + Design + QA) - (C) Customer-facing teams (CS, Support, Sales) - (D) New hires (onboarding context) 3. **Is this compliance-relevant?** Does this process touch regulated data, key integrations, multi-entity, or regulatory requirements? (See `domain-context.md`) Wait for answers before proceeding. --- ### Step 2: Process Discovery Before writing, extract the process structure. Ask: - **What triggers this process?** (Event, schedule, request, threshold) - **What's the end state?** (What does "done" look like?) - **What are the main steps?** (Even rough — I'll structure them) - **Where does it break?** (Known failure points, ambiguities, "it depends" moments) If the user doesn't have clean answers, help them discover the process through structured questions. --- ### Step 3: Generate the Document Choose the appropriate format based on complexity: --- ## Format A: Quick Checklist (< 10 steps, no branching) ```markdown # [Process Name] — Checklist **Owner:** [Role] **Trigger:** [What starts this] **Frequency:** [How often] **Last Updated:** [Date] | **Next Review:** [Date] ## Pre-Conditions - [ ] [Condition that must be true before starting] - [ ] [Required access/tools/approvals] ## Steps - [ ] **Step 1**: [Action] — Owner: [Role] - [ ] **Step 2**: [Action] — Owner: [Role] - [ ] **Step 3**: [Action] — Owner: [Role] ... ## Post-Conditions - [ ] [Verification that process completed correctly] - [ ] [Notification/handoff to next process] ## If Something Goes Wrong - [Common failure]: [What to do] - [Escalation path]: [Who to contact] ``` --- ## Format B: Standard SOP (10-25 steps, some branching) ```markdown # SOP: [Process Name] ## Document Control | Field | Value | |-------|-------| | Version | [1.0] | | Owner | [Role] | | Approved By | [Role] | | Effective Date | [Date] | | Review Cycle | [Quarterly / Semi-annual / Annual] | | Next Review | [Date] | ## Purpose [1-2 sentences: Why this process exists and what outcome it produces.] ## Scope - **Applies to**: [Teams, products, scenarios] - **Does NOT apply to**: [Exclusions — equally important] ## Definitions | Term | Definition | |------|-----------| | [Term] | [Definition — only include terms that aren't obvious] | ## Roles and Responsibilities | Role | Responsibility in This Process | |------|-------------------------------| | [Role] | [What they do] | | [Role] | [What they do] | ## Trigger [What event, schedule, or condition starts this process.] ## Process Steps ### Phase 1: [Phase Name] **Step 1.1: [Action]** - Owner: [Role] - Input: [What you need] - Action: [Detailed instruction] - Output: [What this step produces] - Time estimate: [Duration] **Step 1.2: [Action]** ... ### Decision Point: [Decision Name] ``` IF [condition A] → Go to Phase 2A IF [condition B] → Go to Phase 2B IF [unclear] → Escalate to [Role] ``` **Decision criteria:** - [Condition A]: [Specific, measurable criteria] - [Condition B]: [Specific, measurable criteria] ### Phase 2A: [Branch A Name] ... ### Phase 2B: [Branch B Name] ... ## Compliance Checkpoints > Include only if process is compliance-relevant (see `domain-context.md`). | Checkpoint | Requirement | Verification | Owner | |-----------|-------------|--------------|-------| | [checkpoint] | [Regulation]: [requirement] | [How to verify] | [Role] | | [checkpoint] | [Regulation]: [requirement] | [How to verify] | [Role] | ## Quality Checks - [ ] [Verification step 1] - [ ] [Verification step 2] - [ ] [Final sign-off] ## Exception Handling | Exception | Symptoms | Resolution | Escalation | |-----------|----------|------------|------------| | [exception] | [how you notice it] | [what to do] | [who to call] | | [exception] | [how you notice it] | [what to do] | [who to call] | ## Metrics | Metric | Type | Target | How Measured | |--------|------|--------|-------------| | [metric] | Leading | [target] | [source] | | [metric] | Lagging | [target] | [source] | ## Appendix - [Links to templates, tools, reference docs] - [Related SOPs] ``` --- ## Format C: Runbook (Operational, incident-response style) ```markdown # Runbook: [Process Name] **Criticality:** [High / Medium / Low] **On-Call Owner:** [Role/Team] **Last Tested:** [Date] ## When to Use This Runbook [Specific trigger conditions — be precise.] ## Pre-Flight Checks - [ ] [Access verified] - [ ] [Tools available] - [ ] [Communication channels open] ## Procedure ### Step 1: [Action] ```command or action``` **Expected result:** [What you should see] **If unexpected:** [What to do — don't leave the operator guessing] ### Step 2: [Action] ```command or action``` **Expected result:** [What you should see] **If unexpected:** [What to do] ### Step 3: Decision Point - **If [condition]**: Proceed to Step 4 - **If [condition]**: Skip to Step 6 - **If unsure**: STOP. Escalate to [contact]. ### Step 4: [Action] ... ## Rollback Procedure If the process needs to be reversed: 1. [Rollback step 1] 2. [Rollback step 2] 3. [Verify rollback successful] ## Communication Template ``` Subject: [Process Name] — [Status] To: [Stakeholders] Body: - What: [description] - Impact: [who/what is affected] - Status: [current state] - ETA: [when resolved] - Next update: [time] ``` ## Post-Execution - [ ] Verify success criteria met - [ ] Update status in [tracking system] - [ ] Notify stakeholders - [ ] Log any deviations for process improvement ``` --- ## Process Quality Criteria After generating the doc, self-check against: 1. **Could a new hire follow this?** If not, add more detail at ambiguous points. 2. **Are all decision points explicit?** No "use your judgment" without criteria. 3. **Is every step owned?** "The team" is not an owner. 4. **Are failure modes covered?** What happens when step 3 fails? 5. **Is there a review date?** A process doc without a review cycle decays. 6. **Are compliance checkpoints included?** (If compliance-relevant per `domain-context.md`) --- ## Output Delivery Ask: **Where should I deliver this?** - **Chat**: Full document right here - **File**: Generate a markdown file - **Notion**: Structured for Notion page creation Default to chat unless specified.
Wersje
W bazie nie ma innych skilli o nazwie pm-process-docs.
Migawka bazy z 13.11.2026 · wersja paczki a3098aba1197 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95memstack-business-sop-builder
Dokumentuje powtarzalne procesy jako instrukcje krok po kroku, czyli SOP i runbooki. - 100process-doc
Dokumentuje powtarzalne procesy jako instrukcje SOP krok po kroku z punktami decyzyjnymi, przypadkami brzegowymi i nazwanym właścicielem, aby każdy mógł wykonać proces poprawnie bez pytania. - 100runbook-playbook-production-sop-authoring
Pisze jednoznaczne, krok po kroku runbooki i procedury produkcyjne SOP. - 100ops
Pisze dokumenty operacyjne dla zespołów nietechnicznych i międzydziałowych: SOP, opisy procesów, runbooki, instrukcje oraz dokumenty przekazania i eskalacji. - 100keel-process
Dokumentuje lub przeprojektowuje proces biznesowy: procedura SOP, mapa procesu, RACI i przypisanie właścicieli. - 100sop-writer
Pisze instrukcję operacyjną lub runbook, który może wykonać inna osoba, na podstawie opisu procesu.