Collaborative document writing with structured workflow. Activates for "write document", "draft proposal", "create spec", "documentation", "co-author", "help me write", "RFC", "design doc".
Start with meta-context questions:
Then info dump:
Clarifying questions:
For each section:
1. ASK clarifying questions for this section
2. BRAINSTORM 5-20 options/approaches
3. CURATE down to best options
4. DRAFT the section
5. REFINE based on feedback
Feedback guidance:
Surgical edits:
Fresh perspective test:
Predicted questions:
Q: What problem does this solve?
A: [Answer from doc - check clarity]
Q: Why this approach vs alternatives?
A: [Answer from doc - check completeness]
Q: What are the risks?
A: [Answer from doc - check thoroughness]
# [Feature Name] - Technical Specification
## Status
Draft | Review | Approved | Implemented
## Summary
[1-2 sentence overview]
## Background
[Context and problem statement]
## Goals
- [Goal 1]
- [Goal 2]
## Non-Goals
- [What this does NOT address]
## Proposed Solution
[Detailed description]
### Architecture
[Diagrams, components, data flow]
### API Changes
[Endpoints, schemas, breaking changes]
## Alternatives Considered
### Option A: [Name]
- Pros: [...]
- Cons: [...]
### Option B: [Name]
- Pros: [...]
- Cons: [...]
## Security Considerations
[Auth, data protection, attack vectors]
## Testing Plan
[How to verify correctness]
## Rollout Plan
[Phased rollout, feature flags, rollback]
## Open Questions
- [ ] [Question 1]
- [ ] [Question 2]
# ADR-[NUMBER]: [Title]
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
[What is the issue motivating this decision?]
## Decision
[What is the change being proposed?]
## Consequences
### Positive
- [Benefit 1]
- [Benefit 2]
### Negative
- [Tradeoff 1]
- [Tradeoff 2]
### Neutral
- [Observation 1]
## Alternatives Considered
[Other options and why not chosen]
# [Project Name] Proposal
## Executive Summary
[2-3 sentences for decision makers]
## Problem Statement
[What pain point are we addressing?]
## Proposed Solution
[High-level approach]
## Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| [Metric 1] | X | Y |
## Timeline
| Phase | Deliverable | Date |
|-------|-------------|------|
| Phase 1 | MVP | Week 2 |
## Resources Required
- Engineering: [X weeks]
- Design: [Y weeks]
- Other: [...]
## Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk 1] | High | [Plan] |
## Appendix
[Supporting details, research, data]
| Issue | Solution | |-------|----------| | Too vague | Add concrete examples | | Too detailed | Move to appendix | | Missing context | Add Background section | | No clear ask | Add explicit Proposal | | Buried conclusion | Lead with Summary |
## Document: [Title]
### Stage: [1-Context | 2-Drafting | 3-Review]
### Current Section
[Section being worked on]
### Questions for You
1. [Question 1]
2. [Question 2]
### Draft
[Current draft content]
### Feedback Requested
- Is the tone right?
- What's missing?
- Any concerns?
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity