diff --git a/plugins/pm-engineering/skills/api-docs-writer/SKILL.md b/plugins/pm-engineering/skills/api-docs-writer/SKILL.md index e6d9977..8953450 100644 --- a/plugins/pm-engineering/skills/api-docs-writer/SKILL.md +++ b/plugins/pm-engineering/skills/api-docs-writer/SKILL.md @@ -137,3 +137,9 @@ data = response.json() - [ ] Auth method is clearly stated at the top - [ ] Enum values are listed where applicable - [ ] Pagination documented if the endpoint is a list endpoint + +## Usage Examples +- "Document this API endpoint: [paste spec or description]" +- "Turn this Postman collection into developer docs" +- "Write API reference docs for [endpoint]" +- "Write a developer guide for our [product] API" diff --git a/plugins/pm-engineering/skills/architecture-decision-record/SKILL.md b/plugins/pm-engineering/skills/architecture-decision-record/SKILL.md index a61c362..e0e3d71 100644 --- a/plugins/pm-engineering/skills/architecture-decision-record/SKILL.md +++ b/plugins/pm-engineering/skills/architecture-decision-record/SKILL.md @@ -108,3 +108,9 @@ For each option, produce: - [ ] Decision is stated in plain language in the Decision section - [ ] Risks section identifies what would invalidate this decision - [ ] Written for someone with no prior context on this decision + +## Usage Examples +- "Write an ADR for using [technology]" +- "Document our decision to [architectural choice]" +- "Create an architecture decision record for [topic]" +- "Help me write up why we chose [option] over [alternative]" diff --git a/plugins/pm-engineering/skills/changelog-generator/SKILL.md b/plugins/pm-engineering/skills/changelog-generator/SKILL.md index 5716403..d2c6c03 100644 --- a/plugins/pm-engineering/skills/changelog-generator/SKILL.md +++ b/plugins/pm-engineering/skills/changelog-generator/SKILL.md @@ -73,3 +73,10 @@ Follow [Keep a Changelog](https://keepachangelog.com) format: - [ ] Version and date header is correct - [ ] Empty sections are omitted - [ ] Tone is imperative mood throughout + +## Usage Examples +- "Write a changelog for version [X]" + [paste commits] +- "Generate release notes from these commits" +- "Turn this git log into a CHANGELOG entry" +- "Write the CHANGELOG.md update for this release" +- "What changed in this release?" + [paste commit list] diff --git a/plugins/pm-engineering/skills/code-review-checklist/SKILL.md b/plugins/pm-engineering/skills/code-review-checklist/SKILL.md index 29edd69..cb4e9da 100644 --- a/plugins/pm-engineering/skills/code-review-checklist/SKILL.md +++ b/plugins/pm-engineering/skills/code-review-checklist/SKILL.md @@ -103,3 +103,9 @@ Based on the change type and language, flag 2-3 things reviewers typically miss - [ ] Change-type-specific section is included - [ ] Risk-appropriate depth matches stated risk level - [ ] Decision framework is explicit + +## Usage Examples +- "Generate a code review checklist for [PR description]" +- "What should I check in this pull request?" +- "Give me a code review checklist for a [language] [change type]" +- "Review checklist for a high-risk PR in [language]" diff --git a/plugins/pm-engineering/skills/debugging-log-analyser/SKILL.md b/plugins/pm-engineering/skills/debugging-log-analyser/SKILL.md index ffeb2b3..21ff6a2 100644 --- a/plugins/pm-engineering/skills/debugging-log-analyser/SKILL.md +++ b/plugins/pm-engineering/skills/debugging-log-analyser/SKILL.md @@ -75,3 +75,10 @@ One or two concrete things that would prevent this class of error recurring: - [ ] Next steps are actionable commands, not vague advice - [ ] Language-specific idioms are used correctly - [ ] Prevention is proactive (not just "add error handling") + +## Usage Examples +- "Why is this crashing?" + [paste log] +- "Can you analyse this stack trace?" +- "I'm getting this error, what does it mean?" +- "Debug this log for me" +- "What's causing this exception?" diff --git a/plugins/pm-engineering/skills/incident-postmortem/SKILL.md b/plugins/pm-engineering/skills/incident-postmortem/SKILL.md index af1e3ff..2a4a153 100644 --- a/plugins/pm-engineering/skills/incident-postmortem/SKILL.md +++ b/plugins/pm-engineering/skills/incident-postmortem/SKILL.md @@ -135,3 +135,9 @@ Rules for action items: - [ ] Every action item has an owner and due date - [ ] "What went well" section is genuine, not token - [ ] Executive summary is readable by non-technical leadership + +## Usage Examples +- "Write a postmortem for the [incident name] outage" +- "Help me write a P1 incident report" +- "Generate an RCA document for [service] going down on [date]" +- "Draft a blameless postmortem from these notes: [paste notes]" diff --git a/plugins/pm-engineering/skills/pr-description-writer/SKILL.md b/plugins/pm-engineering/skills/pr-description-writer/SKILL.md index f488f07..89f5e3c 100644 --- a/plugins/pm-engineering/skills/pr-description-writer/SKILL.md +++ b/plugins/pm-engineering/skills/pr-description-writer/SKILL.md @@ -78,3 +78,10 @@ Flag anything that warrants extra attention: - [ ] Changes list describes logical changes (not file-by-file changes) - [ ] Testing steps are reproducible by someone unfamiliar with the code - [ ] Risk-appropriate reviewer guidance is included + +## Usage Examples +- "Write a PR description for these changes" + [paste diff or description] +- "Draft a pull request for [feature]" +- "I need a PR description — here's what I changed" +- "Summarise these commits into a PR description" +- "Write the PR body for this branch" diff --git a/plugins/pm-engineering/skills/runbook-writer/SKILL.md b/plugins/pm-engineering/skills/runbook-writer/SKILL.md index 4571add..83a52f2 100644 --- a/plugins/pm-engineering/skills/runbook-writer/SKILL.md +++ b/plugins/pm-engineering/skills/runbook-writer/SKILL.md @@ -135,3 +135,10 @@ After completing the runbook: - [ ] Rollback procedure is complete and independently testable - [ ] Escalation paths name specific contacts, not just team names - [ ] Runbook can be followed by someone who has never touched this system + +## Usage Examples +- "Write a runbook for [service] deployment" +- "Create an incident response runbook for [alert type]" +- "I need a runbook for [procedure]" +- "Document the operational procedure for [X]" +- "Write an ops playbook for [scenario]" diff --git a/plugins/pm-engineering/skills/system-design-interview/SKILL.md b/plugins/pm-engineering/skills/system-design-interview/SKILL.md index 496cedb..e2c74e9 100644 --- a/plugins/pm-engineering/skills/system-design-interview/SKILL.md +++ b/plugins/pm-engineering/skills/system-design-interview/SKILL.md @@ -126,3 +126,10 @@ Things to tackle in production but out of scope for this design session: - [ ] At least 2 component deep-dives with technology choices justified - [ ] Trade-offs section is honest (not just benefits of chosen approach) - [ ] Data flow is described end-to-end for the critical path + +## Usage Examples +- "Help me answer a system design interview: [question]" +- "Design [system] for a system design interview" +- "How would I architect [system] at scale?" +- "I have a system design interview — the question is [X]" +- "Design a [URL shortener / chat system / notification service / feed]" diff --git a/plugins/pm-engineering/skills/test-strategy-doc/SKILL.md b/plugins/pm-engineering/skills/test-strategy-doc/SKILL.md index bcfd3dc..d01f9b1 100644 --- a/plugins/pm-engineering/skills/test-strategy-doc/SKILL.md +++ b/plugins/pm-engineering/skills/test-strategy-doc/SKILL.md @@ -118,3 +118,10 @@ Testing is complete when: - [ ] P0 test cases cover the highest-risk paths specifically - [ ] Each test type names a concrete tool (not "some testing framework") - [ ] Definition of Done is measurable (not "tests are done when QA is happy") + +## Usage Examples +- "Write a test strategy for [feature]" + [paste spec or PRD] +- "Create a test plan for [system]" +- "How should we test [feature]?" +- "I need a QA plan for this sprint" +- "What tests do we need for [X]?" diff --git a/skills/api-docs-writer/SKILL.md b/skills/api-docs-writer/SKILL.md index e6d9977..8953450 100644 --- a/skills/api-docs-writer/SKILL.md +++ b/skills/api-docs-writer/SKILL.md @@ -137,3 +137,9 @@ data = response.json() - [ ] Auth method is clearly stated at the top - [ ] Enum values are listed where applicable - [ ] Pagination documented if the endpoint is a list endpoint + +## Usage Examples +- "Document this API endpoint: [paste spec or description]" +- "Turn this Postman collection into developer docs" +- "Write API reference docs for [endpoint]" +- "Write a developer guide for our [product] API" diff --git a/skills/architecture-decision-record/SKILL.md b/skills/architecture-decision-record/SKILL.md index a61c362..e0e3d71 100644 --- a/skills/architecture-decision-record/SKILL.md +++ b/skills/architecture-decision-record/SKILL.md @@ -108,3 +108,9 @@ For each option, produce: - [ ] Decision is stated in plain language in the Decision section - [ ] Risks section identifies what would invalidate this decision - [ ] Written for someone with no prior context on this decision + +## Usage Examples +- "Write an ADR for using [technology]" +- "Document our decision to [architectural choice]" +- "Create an architecture decision record for [topic]" +- "Help me write up why we chose [option] over [alternative]" diff --git a/skills/changelog-generator/SKILL.md b/skills/changelog-generator/SKILL.md index 5716403..d2c6c03 100644 --- a/skills/changelog-generator/SKILL.md +++ b/skills/changelog-generator/SKILL.md @@ -73,3 +73,10 @@ Follow [Keep a Changelog](https://keepachangelog.com) format: - [ ] Version and date header is correct - [ ] Empty sections are omitted - [ ] Tone is imperative mood throughout + +## Usage Examples +- "Write a changelog for version [X]" + [paste commits] +- "Generate release notes from these commits" +- "Turn this git log into a CHANGELOG entry" +- "Write the CHANGELOG.md update for this release" +- "What changed in this release?" + [paste commit list] diff --git a/skills/code-review-checklist/SKILL.md b/skills/code-review-checklist/SKILL.md index 29edd69..cb4e9da 100644 --- a/skills/code-review-checklist/SKILL.md +++ b/skills/code-review-checklist/SKILL.md @@ -103,3 +103,9 @@ Based on the change type and language, flag 2-3 things reviewers typically miss - [ ] Change-type-specific section is included - [ ] Risk-appropriate depth matches stated risk level - [ ] Decision framework is explicit + +## Usage Examples +- "Generate a code review checklist for [PR description]" +- "What should I check in this pull request?" +- "Give me a code review checklist for a [language] [change type]" +- "Review checklist for a high-risk PR in [language]" diff --git a/skills/debugging-log-analyser/SKILL.md b/skills/debugging-log-analyser/SKILL.md index ffeb2b3..21ff6a2 100644 --- a/skills/debugging-log-analyser/SKILL.md +++ b/skills/debugging-log-analyser/SKILL.md @@ -75,3 +75,10 @@ One or two concrete things that would prevent this class of error recurring: - [ ] Next steps are actionable commands, not vague advice - [ ] Language-specific idioms are used correctly - [ ] Prevention is proactive (not just "add error handling") + +## Usage Examples +- "Why is this crashing?" + [paste log] +- "Can you analyse this stack trace?" +- "I'm getting this error, what does it mean?" +- "Debug this log for me" +- "What's causing this exception?" diff --git a/skills/incident-postmortem/SKILL.md b/skills/incident-postmortem/SKILL.md index af1e3ff..2a4a153 100644 --- a/skills/incident-postmortem/SKILL.md +++ b/skills/incident-postmortem/SKILL.md @@ -135,3 +135,9 @@ Rules for action items: - [ ] Every action item has an owner and due date - [ ] "What went well" section is genuine, not token - [ ] Executive summary is readable by non-technical leadership + +## Usage Examples +- "Write a postmortem for the [incident name] outage" +- "Help me write a P1 incident report" +- "Generate an RCA document for [service] going down on [date]" +- "Draft a blameless postmortem from these notes: [paste notes]" diff --git a/skills/pr-description-writer/SKILL.md b/skills/pr-description-writer/SKILL.md index f488f07..89f5e3c 100644 --- a/skills/pr-description-writer/SKILL.md +++ b/skills/pr-description-writer/SKILL.md @@ -78,3 +78,10 @@ Flag anything that warrants extra attention: - [ ] Changes list describes logical changes (not file-by-file changes) - [ ] Testing steps are reproducible by someone unfamiliar with the code - [ ] Risk-appropriate reviewer guidance is included + +## Usage Examples +- "Write a PR description for these changes" + [paste diff or description] +- "Draft a pull request for [feature]" +- "I need a PR description — here's what I changed" +- "Summarise these commits into a PR description" +- "Write the PR body for this branch" diff --git a/skills/runbook-writer/SKILL.md b/skills/runbook-writer/SKILL.md index 4571add..83a52f2 100644 --- a/skills/runbook-writer/SKILL.md +++ b/skills/runbook-writer/SKILL.md @@ -135,3 +135,10 @@ After completing the runbook: - [ ] Rollback procedure is complete and independently testable - [ ] Escalation paths name specific contacts, not just team names - [ ] Runbook can be followed by someone who has never touched this system + +## Usage Examples +- "Write a runbook for [service] deployment" +- "Create an incident response runbook for [alert type]" +- "I need a runbook for [procedure]" +- "Document the operational procedure for [X]" +- "Write an ops playbook for [scenario]" diff --git a/skills/system-design-interview/SKILL.md b/skills/system-design-interview/SKILL.md index 496cedb..e2c74e9 100644 --- a/skills/system-design-interview/SKILL.md +++ b/skills/system-design-interview/SKILL.md @@ -126,3 +126,10 @@ Things to tackle in production but out of scope for this design session: - [ ] At least 2 component deep-dives with technology choices justified - [ ] Trade-offs section is honest (not just benefits of chosen approach) - [ ] Data flow is described end-to-end for the critical path + +## Usage Examples +- "Help me answer a system design interview: [question]" +- "Design [system] for a system design interview" +- "How would I architect [system] at scale?" +- "I have a system design interview — the question is [X]" +- "Design a [URL shortener / chat system / notification service / feed]" diff --git a/skills/test-strategy-doc/SKILL.md b/skills/test-strategy-doc/SKILL.md index bcfd3dc..d01f9b1 100644 --- a/skills/test-strategy-doc/SKILL.md +++ b/skills/test-strategy-doc/SKILL.md @@ -118,3 +118,10 @@ Testing is complete when: - [ ] P0 test cases cover the highest-risk paths specifically - [ ] Each test type names a concrete tool (not "some testing framework") - [ ] Definition of Done is measurable (not "tests are done when QA is happy") + +## Usage Examples +- "Write a test strategy for [feature]" + [paste spec or PRD] +- "Create a test plan for [system]" +- "How should we test [feature]?" +- "I need a QA plan for this sprint" +- "What tests do we need for [X]?"