Internal Writing

Internal Writing

Draft internal communications and reviews. This is a router — pick one branch, then load only its references.

When NOT to use

• External/customer-facing communications
• Technical documentation, API docs, changelogs
• Marketing, sales, or press copy

Workflow — pick branch first

| Signal | Branch | Load | |---|---| | Meeting transcript / raw notes / agenda | meeting-minutes | references/minutes-schema.md | | Self-assessment / peer / upward / brag sheet / promotion | performance-review | references/output-schemas.md | | Team update (3P) / newsletter / FAQ / general comms | internal-comms | examples/3p-updates.md etc. | | Unsure | Ask: "minutes, review, or comms?" — one question, then route | — |

Only load the references for the chosen branch — don't preload all three.

Branch — meeting-minutes

Produce concise minutes for internal meetings, prioritizing decisions and action items.

Output schema

Required sections:

• Metadata
• Attendance
• Decisions (with rationale)
• Action items (owner + due date + acceptance criteria)
• Parking lot for unresolved items

See references/minutes-schema.md for full structure.

Style rules

• Keep it under one page for 30-minute meetings, two pages for 60-minute meetings.
• Use plain language and bullets.
• No speculation; label uncertain items TBD.
• No personal opinions.
• Link to artifacts when available.

Completion criteria

• Required sections are present.
• Every action item has an owner and due date/timeframe.
• Decisions include rationale.
• Uncertain items are labeled TBD.

Branch — performance-review

Draft self-assessments, peer reviews, upward feedback, and evidence-backed brag sheets or weekly updates. Enforces a 3-part impact contract: action → result → evidence.

Review types

Workflow

1. Gather context — review type, subject, period.
2. Surface evidence — pull metrics or git/GitHub PRs; never fabricate.
3. Draft — STAR for achievements, impact-first bullets for brag sheets.
4. Output — present with evidence summary, mark [NEEDS DETAIL], save to outputs/<year>/<month>/.

Output schemas

See references/output-schemas.md for self-assessment, peer review, and upward feedback templates.

Important rules

• Never submit reviews — only draft files.
• Keep peer/upward feedback focused on observable behaviours, not personality.
• Decline dishonest or personal-attack framing; offer constructive reframing.
• Respect confidentiality.

Branch — internal-comms

Write internal communications following the formats in examples/.

1. Identify the communication type from the request.
2. Load the matching guideline from examples/:
   • examples/3p-updates.md — Progress/Plans/Problems team updates
   • examples/company-newsletter.md — company-wide newsletters
   • examples/faq-answers.md — answering frequently asked questions
   • examples/general-comms.md — anything else
3. Follow the specific instructions for formatting, tone, and content gathering.
4. Ask for clarification if the type doesn't match any guideline.

Completion criteria

• The draft matches the selected guideline's formatting and tone.
• All required sections are present.
• The user confirms the draft is ready to send.

Top-level completion criteria

• Branch chosen before any drafting (no mixing branches)
• Only the chosen branch's references loaded
• Branch-specific completion criteria met (see above)

Related skills

• documentation-writer — external/software docs.
• ml-paper-writing — academic papers, not internal prose.