Team Collaboration & Document Management

Help me create a 'New Employee Onboarding Guide':

Input documents:
- Company policy document (policy.pdf)
- Tech stack overview (tech_stack.md)
- FAQ (faq.docx)
- Team contacts (contacts.xlsx)

Output requirements:
- Markdown format with clear section structure
- Extract key information and remove redundancy
- Add table of contents and quick index
- Add "Further Reading" links at the end of each section
- Finally generate a PDF version

This is the transcript of today's product meeting:
[Paste transcript]

Please:
1. Summarize key discussion points
2. Extract all action items and label owners and due dates
3. Identify unresolved issues
4. Generate structured meeting minutes
5. Create a task-tracking table (CSV format) that can be
   imported into Asana/Jira

team-knowledge-base/
├── prompts/
│   ├── code-review-checklist.md
│   ├── bug-report-template.md
│   └── feature-spec-template.md
├── skills/
│   ├── team-report-generator/
│   └── sprint-summary/
└── guides/
    ├── onboarding-guide.md
    └── common-workflows.md

After completing [task] using Happycapy:

1. Summarize what we accomplished
2. Document the workflow used
3. Note any challenges and how we solved them
4. Update team documentation with learnings
5. Suggest any improvements for next time

Create a comprehensive project handoff document:

Project: [project name]
Context: [brief description]

Include documents from:
- Architecture decisions (architecture.md)
- API documentation (swagger.yaml)
- Database schema (schema.sql)
- Deployment guides (deploy-notes.md)
- Known issues (issues.md)

Generate:
1. Executive Summary (for stakeholders)
2. Technical Overview (for engineers)
3. Quick Start Guide (for new team members)
4. Troubleshooting Guide (common issues + solutions)
5. Future Roadmap (planned improvements)

Format: Markdown + PDF
Tone: Clear, concise, assumes reader is smart but unfamiliar
      with the project

Process our sprint retrospective notes:

[Paste raw notes or upload document]

Create:
1. Summary of what went well
2. Summary of challenges faced
3. Action items with owners and deadlines
4. Metrics comparison (planned vs. actual)
5. Key learnings
6. Carry-over items for next sprint

Format as:
- Markdown document for team reference
- Presentation slides for stakeholder update
- CSV of action items for project management tool

Create a knowledge base article from this support thread:

[Paste support conversation]

Article should include:
1. Problem statement (what was the issue?)
2. Root cause (why did it happen?)
3. Solution (step-by-step instructions)
4. Prevention (how to avoid in future)
5. Related issues (links to similar problems)

Format:
- Clear headings
- Code blocks for technical instructions
- Screenshots references (describe what should be shown)
- Search-friendly keywords

Audience: Technical support team and advanced users

Our team wiki is outdated. Help me update it:

Current wiki: [provide link or paste content]

Recent changes:
- New team members: [list]
- Deprecated tools: [list]
- New processes: [describe]
- Updated contact information: [provide]

Please:
1. Identify outdated sections
2. Suggest updates for each section
3. Reorganize for better navigation
4. Add missing information
5. Remove redundant content
6. Ensure consistent formatting

Output updated wiki content in Markdown.

Create an alignment document for cross-team project:

Teams involved:
- Engineering: [focus area]
- Design: [focus area]
- Product: [focus area]
- Marketing: [focus area]

Project: [description]

Document should include:
1. Shared goals and success metrics
2. Each team's responsibilities
3. Dependencies between teams
4. Communication protocols
5. Timeline and milestones
6. Decision-making process
7. Risk assessment

Format: Collaborative document that all teams can reference
Tone: Clear, neutral, focuses on alignment not blame

Help me set up documentation workflow with version control:

Requirements:
1. Markdown-based documentation
2. Git version control
3. Automatic table of contents generation
4. Link validation
5. Change log generation

Set up:
- Directory structure
- Pre-commit hooks for validation
- GitHub Actions for automated checks
- Contributing guidelines for team

Provide setup instructions and templates.

Generate weekly team status report:

Data sources:
- GitHub: PRs merged, issues closed
- Jira: Tickets completed, in progress
- Team calendar: Key meetings and decisions

Report format:
1. Executive Summary
   - Key accomplishments
   - Notable blockers
   - Next week's priorities

2. Detailed Metrics
   - Velocity (story points completed)
   - Bug resolution rate
   - PR review turnaround time

3. Team Highlights
   - Individual contributions
   - Learning and development

4. Upcoming
   - Next sprint goals
   - Key dates and deadlines

Automate this to run every Friday at 4pm. (Pro/Max plan)

Create an automated onboarding workflow for new engineers:

Day 1 tasks:
- Account setup guide (step-by-step)
- Development environment setup
- First commit tutorial
- Team introduction

Week 1 tasks:
- Codebase architecture overview
- Common workflows documentation
- Starter tasks (good first issues)

Week 2-4 tasks:
- Progressive complexity tasks
- Mentorship pairing schedule
- Check-in points

Generate:
1. New hire checklist
2. Automated email sequence (draft content)
3. Slack messages to send at key points
4. Manager check-in guide

Make it comprehensive but not overwhelming.

Document this architectural decision:

Context: [describe situation]
Options considered: [list options]
Decision: [what we chose]
Rationale: [why we chose it]

Format as Architecture Decision Record (ADR):
- Title: [concise description]
- Status: [proposed/accepted/deprecated]
- Context: [background and constraints]
- Decision: [what we decided]
- Consequences: [positive and negative outcomes]
- Alternatives: [what we didn't choose and why]

Add to our ADR collection in docs/decisions/

Facilitate cross-functional planning session:

Goal: Plan Q2 product launch

Participants:
- Engineering: [team size and focus]
- Design: [team size and focus]
- Product: [priorities]
- Marketing: [priorities]

Help me:
1. Create planning session agenda
2. Generate discussion prompts for each function
3. Create dependency mapping template
4. Timeline visualization (Gantt chart data)
5. Resource allocation planning
6. Risk identification framework
7. Success metrics definition

Output:
- Pre-read document for participants
- Session facilitation guide
- Templates for capturing decisions
- Post-session summary format

Create a reusable template for [document type]:

Standard sections:
- [list required sections]

Optional sections:
- [list optional sections]

Include:
- Markdown template file
- Usage instructions
- Example filled-in version
- Checklist for completeness

Save in team templates repository.

Set up documentation review workflow:

1. Author creates draft
2. Peer review (technical accuracy)
3. Editor review (clarity, grammar)
4. Stakeholder review (alignment)
5. Final approval

Create:
- Review checklist for each stage
- Feedback template
- Approval process
- Version tracking system

Integrate with our existing tools: [list tools]

Convert this Slack discussion into a decision document:

[Paste Slack conversation]

Extract:
1. Problem being discussed
2. Proposed solutions
3. Concerns raised
4. Final decision
5. Action items

Format as a durable document that can be referenced later,
so people don't need to dig through Slack history.

Review our team's documentation practices:

Current state:
- Tools we use: [list]
- Pain points: [list]
- What works well: [list]

Suggest improvements:
1. Process optimizations
2. Tool integrations
3. Template updates
4. Training needs

Prioritize by: impact vs. effort