opencode-knowledge-work 0.0.0-stage → 0.1.1

package/content/engineering/skills/engineering-documentation/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: documentation
+description: Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
+---
+
+# Technical Documentation
+
+Write clear, maintainable technical documentation for different audiences and purposes.
+
+## Document Types
+
+### README
+- What this is and why it exists
+- Quick start (< 5 minutes to first success)
+- Configuration and usage
+- Contributing guide
+
+### API Documentation
+- Endpoint reference with request/response examples
+- Authentication and error codes
+- Rate limits and pagination
+- SDK examples
+
+### Runbook
+- When to use this runbook
+- Prerequisites and access needed
+- Step-by-step procedure
+- Rollback steps
+- Escalation path
+
+### Architecture Doc
+- Context and goals
+- High-level design with diagrams
+- Key decisions and trade-offs
+- Data flow and integration points
+
+### Onboarding Guide
+- Environment setup
+- Key systems and how they connect
+- Common tasks with walkthroughs
+- Who to ask for what
+
+## Principles
+
+1. **Write for the reader** — Who is reading this and what do they need?
+2. **Start with the most useful information** — Don't bury the lede
+3. **Show, don't tell** — Code examples, commands, screenshots
+4. **Keep it current** — Outdated docs are worse than no docs
+5. **Link, don't duplicate** — Reference other docs instead of copying

package/content/engineering/skills/engineering-incident-response/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: incident-response
+description: Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
+argument-hint: "<incident description or alert>"
+---
+
+# /incident-response
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
+
+Manage an incident from detection through postmortem.
+
+## Usage
+
+```
+/incident-response $ARGUMENTS
+```
+
+## Modes
+
+```
+/incident-response new [description]     # Start a new incident
+/incident-response update [status]       # Post a status update
+/incident-response postmortem            # Generate postmortem from incident data
+```
+
+If no mode is specified, ask what phase the incident is in.
+
+## How It Works
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│                    INCIDENT RESPONSE                               │
+├─────────────────────────────────────────────────────────────────┤
+│  Phase 1: TRIAGE                                                  │
+│  ✓ Assess severity (SEV1-4)                                     │
+│  ✓ Identify affected systems and users                          │
+│  ✓ Assign roles (IC, comms, responders)                         │
+│                                                                    │
+│  Phase 2: COMMUNICATE                                              │
+│  ✓ Draft internal status update                                  │
+│  ✓ Draft customer communication (if needed)                     │
+│  ✓ Set up war room and cadence                                   │
+│                                                                    │
+│  Phase 3: MITIGATE                                                 │
+│  ✓ Document mitigation steps taken                               │
+│  ✓ Track timeline of events                                      │
+│  ✓ Confirm resolution                                            │
+│                                                                    │
+│  Phase 4: POSTMORTEM                                               │
+│  ✓ Blameless postmortem document                                 │
+│  ✓ Timeline reconstruction                                       │
+│  ✓ Root cause analysis (5 whys)                                  │
+│  ✓ Action items with owners                                      │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+## Severity Classification
+
+| Level | Criteria | Response Time |
+|-------|----------|---------------|
+| SEV1 | Service down, all users affected | Immediate, all-hands |
+| SEV2 | Major feature degraded, many users affected | Within 15 min |
+| SEV3 | Minor feature issue, some users affected | Within 1 hour |
+| SEV4 | Cosmetic or low-impact issue | Next business day |
+
+## Communication Guidance
+
+Provide clear, factual updates at regular cadence. Include: what's happening, who's affected, what we're doing, when the next update is.
+
+## Output — Status Update
+
+```markdown
+## Incident Update: [Title]
+**Severity:** SEV[1-4] | **Status:** Investigating | Identified | Monitoring | Resolved
+**Impact:** [Who/what is affected]
+**Last Updated:** [Timestamp]
+
+### Current Status
+[What we know now]
+
+### Actions Taken
+- [Action 1]
+- [Action 2]
+
+### Next Steps
+- [What's happening next and ETA]
+
+### Timeline
+| Time | Event |
+|------|-------|
+| [HH:MM] | [Event] |
+```
+
+## Output — Postmortem
+
+```markdown
+## Postmortem: [Incident Title]
+**Date:** [Date] | **Duration:** [X hours] | **Severity:** SEV[X]
+**Authors:** [Names] | **Status:** Draft
+
+### Summary
+[2-3 sentence plain-language summary]
+
+### Impact
+- [Users affected]
+- [Duration of impact]
+- [Business impact if quantifiable]
+
+### Timeline
+| Time (UTC) | Event |
+|------------|-------|
+| [HH:MM] | [Event] |
+
+### Root Cause
+[Detailed explanation of what caused the incident]
+
+### 5 Whys
+1. Why did [symptom]? → [Because...]
+2. Why did [cause 1]? → [Because...]
+3. Why did [cause 2]? → [Because...]
+4. Why did [cause 3]? → [Because...]
+5. Why did [cause 4]? → [Root cause]
+
+### What Went Well
+- [Things that worked]
+
+### What Went Poorly
+- [Things that didn't work]
+
+### Action Items
+| Action | Owner | Priority | Due Date |
+|--------|-------|----------|----------|
+| [Action] | [Person] | P0/P1/P2 | [Date] |
+
+### Lessons Learned
+[Key takeaways for the team]
+```
+
+## If Connectors Available
+
+If **~~monitoring** is connected:
+- Pull alert details and metrics
+- Show graphs of affected metrics
+
+If **~~incident management** is connected:
+- Create or update incident in PagerDuty/Opsgenie
+- Page on-call responders
+
+If **~~chat** is connected:
+- Post status updates to incident channel
+- Create war room channel
+
+## Tips
+
+1. **Start writing immediately** — Don't wait for complete information. Update as you learn more.
+2. **Keep updates factual** — What we know, what we've done, what's next. No speculation.
+3. **Postmortems are blameless** — Focus on systems and processes, not individuals.

package/content/engineering/skills/engineering-standup/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: standup
+description: Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update.
+argument-hint: "[yesterday | today | blockers]"
+---
+
+# /standup
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
+
+Generate a standup update by pulling together recent activity across your tools.
+
+## How It Works
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│                        STANDUP                                    │
+├─────────────────────────────────────────────────────────────────┤
+│  STANDALONE (always works)                                       │
+│  ✓ Tell me what you worked on and I'll structure it             │
+│  ✓ Format for daily standup (yesterday / today / blockers)      │
+│  ✓ Keep it concise and action-oriented                          │
+├─────────────────────────────────────────────────────────────────┤
+│  SUPERCHARGED (when you connect your tools)                      │
+│  + Source control: Recent commits and PRs                        │
+│  + Project tracker: Ticket status changes                        │
+│  + Chat: Relevant discussions and decisions                      │
+│  + CI/CD: Build and deploy status                                │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+## What I Need From You
+
+**Option A: Let me pull it**
+If your tools are connected, just say `/standup` and I'll gather everything automatically.
+
+**Option B: Tell me what you did**
+"Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue."
+
+## Output
+
+```markdown
+## Standup — [Date]
+
+### Yesterday
+- [Completed item with ticket reference if available]
+- [Completed item]
+
+### Today
+- [Planned item with ticket reference]
+- [Planned item]
+
+### Blockers
+- [Blocker with context and who can help]
+```
+
+## If Connectors Available
+
+If **~~source control** is connected:
+- Pull recent commits and PRs (opened, reviewed, merged)
+- Summarize code changes at a high level
+
+If **~~project tracker** is connected:
+- Pull tickets moved to "in progress" or "done"
+- Show upcoming sprint items
+
+If **~~chat** is connected:
+- Scan for relevant discussions and decisions
+- Flag threads needing your response
+
+## Tips
+
+1. **Run it every morning** — Build a habit and never scramble for standup notes.
+2. **Add context** — After I generate, add any nuance about blockers or priorities.
+3. **Share format** — Ask me to format for Slack, email, or your team's standup tool.

package/content/engineering/skills/engineering-system-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: system-design
+description: Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
+---
+
+# System Design
+
+Help design systems and evaluate architectural decisions.
+
+## Framework
+
+### 1. Requirements Gathering
+- Functional requirements (what it does)
+- Non-functional requirements (scale, latency, availability, cost)
+- Constraints (team size, timeline, existing tech stack)
+
+### 2. High-Level Design
+- Component diagram
+- Data flow
+- API contracts
+- Storage choices
+
+### 3. Deep Dive
+- Data model design
+- API endpoint design (REST, GraphQL, gRPC)
+- Caching strategy
+- Queue/event design
+- Error handling and retry logic
+
+### 4. Scale and Reliability
+- Load estimation
+- Horizontal vs. vertical scaling
+- Failover and redundancy
+- Monitoring and alerting
+
+### 5. Trade-off Analysis
+- Every decision has trade-offs. Make them explicit.
+- Consider: complexity, cost, team familiarity, time to market, maintainability
+
+## Output
+
+Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis. Always identify what you'd revisit as the system grows.

package/content/engineering/skills/engineering-tech-debt/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: tech-debt
+description: Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
+---
+
+# Tech Debt Management
+
+Systematically identify, categorize, and prioritize technical debt.
+
+## Categories
+
+| Type | Examples | Risk |
+|------|----------|------|
+| **Code debt** | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development |
+| **Architecture debt** | Monolith that should be split, wrong data store | Scaling limits |
+| **Test debt** | Low coverage, flaky tests, missing integration tests | Regressions ship |
+| **Dependency debt** | Outdated libraries, unmaintained dependencies | Security vulns |
+| **Documentation debt** | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain |
+| **Infrastructure debt** | Manual deploys, no monitoring, no IaC | Incidents, slow recovery |
+
+## Prioritization Framework
+
+Score each item on:
+- **Impact**: How much does it slow the team down? (1-5)
+- **Risk**: What happens if we don't fix it? (1-5)
+- **Effort**: How hard is the fix? (1-5, inverted — lower effort = higher priority)
+
+Priority = (Impact + Risk) x (6 - Effort)
+
+## Output
+
+Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.

package/content/engineering/skills/engineering-testing-strategy/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: testing-strategy
+description: Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
+---
+
+# Testing Strategy
+
+Design effective testing strategies balancing coverage, speed, and maintenance.
+
+## Testing Pyramid
+
+```
+        /  E2E  \         Few, slow, high confidence
+       / Integration \     Some, medium speed
+      /    Unit Tests  \   Many, fast, focused
+```
+
+## Strategy by Component Type
+
+- **API endpoints**: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers
+- **Data pipelines**: Input validation, transformation correctness, idempotency tests
+- **Frontend**: Component tests, interaction tests, visual regression, accessibility
+- **Infrastructure**: Smoke tests, chaos engineering, load tests
+
+## What to Cover
+
+Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
+
+Skip: trivial getters/setters, framework code, one-off scripts.
+
+## Output
+
+Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.

package/content/enterprise-search/.mcp.json

@@ -0,0 +1,36 @@
+{
+  "mcpServers": {
+    "slack": {
+      "type": "http",
+      "url": "https://mcp.slack.com/mcp",
+      "oauth": {
+        "clientId": "1601185624273.8899143856786",
+        "callbackPort": 3118
+      }
+    },
+    "notion": {
+      "type": "http",
+      "url": "https://mcp.notion.com/mcp"
+    },
+    "guru": {
+      "type": "http",
+      "url": "https://mcp.api.getguru.com/mcp"
+    },
+    "atlassian": {
+      "type": "http",
+      "url": "https://mcp.atlassian.com/v1/mcp"
+    },
+    "asana": {
+      "type": "http",
+      "url": "https://mcp.asana.com/v2/mcp"
+    },
+    "google calendar": {
+      "type": "http",
+      "url": ""
+    },
+    "gmail": {
+      "type": "http",
+      "url": ""
+    }
+  }
+}

package/content/enterprise-search/CONNECTORS.md

@@ -0,0 +1,21 @@
+# Connectors
+
+## How tool references work
+
+Plugin files use `~~category` as a placeholder for whatever tool the user connects in that category. For example, `~~chat` might mean Slack, Microsoft Teams, or any other chat tool with an MCP server.
+
+Plugins are **tool-agnostic** — they describe workflows in terms of categories (chat, email, cloud storage, etc.) rather than specific products. The `.mcp.json` pre-configures specific MCP servers, but any MCP server in that category works.
+
+This plugin uses `~~category` references extensively as source labels in search output (e.g. `~~chat:`, `~~email:`). These are intentional — they represent dynamic category markers that resolve to whatever tool is connected.
+
+## Connectors for this plugin
+
+| Category | Placeholder | Included servers | Other options |
+|----------|-------------|-----------------|---------------|
+| Chat | `~~chat` | Slack | Microsoft Teams, Discord |
+| Email | `~~email` | Microsoft 365 | — |
+| Cloud storage | `~~cloud storage` | Microsoft 365 | Dropbox |
+| Knowledge base | `~~knowledge base` | Notion, Guru | Confluence, Slite |
+| Project tracker | `~~project tracker` | Atlassian (Jira/Confluence), Asana | Linear, monday.com |
+| CRM | `~~CRM` | *(not pre-configured)* | Salesforce, HubSpot |
+| Office suite | `~~office suite` | Microsoft 365 | Google Workspace |

package/content/enterprise-search/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.