skills.rest
snoodleboot-io
snoodleboot-ioOFFICIAL
Explore all skills by this author →
GitHub

team-collaboration

Applies structured practices for code ownership, onboarding, handoffs, and written disagreement in engineering teams.

Updated Dec 29, 2025
Search Tags:#code review#onboarding#handoff#pair programming#rfc#code ownership#distributed teams
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill team-collaboration-snoodleboot-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-collaboration
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/team-collaboration
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill team-collaboration-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lose time to inherited ownership defaults, blocked handoffs, unbounded written disagreements, and RFC processes that never conclude. This Skill provides concrete, opinionated patterns for structuring team collaboration so work moves without depending on any single person. ## Core Features & Use Cases - Ownership Models: Compares strong versus collective ownership and prescribes collective ownership with named rotating stewards, a 24-hour escape hatch, and CODEOWNERS enforcement. - Onboarding and Handoffs: Provides a day-by-day first-week onboarding plan and a structured handoff template covering branch state, next steps, blockers, traps, and open decisions. - Disagreement and Decisions: Defines a two-round rule for written disagreement, objection-strength labeling, disagree-and-commit with revisit triggers, and RFC requirements (named decider, comment deadline, outcome section). - Use Case: A distributed team spanning three time zones uses the vertical-slice splitting guidance and non-blocking question format to cut cross-zone round trips from four days to one. ## Quick Start Ask the assistant to apply the team-collaboration skill to design an ownership and handoff process for your engineering team.

Frequently Asked Questions about team-collaboration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up code ownership without creating bottlenecks?▼

Use collective ownership with named stewards recorded in CODEOWNERS. Anyone may change any file, the steward reviews for trap knowledge rather than style, and a 24-hour escape hatch lets two other engineers approve if the steward does not respond.

What should a good engineering handoff document include?▼

A handoff should transfer state, not status: branch name and CI state, ticket link, completed work, the explicit next step, named blockers, traps and non-obvious failure modes, decisions already made with reasoning, and unresolved open questions.

When is pair programming worth the cost?▼

Pairing pays off for novel design work, onboarding, incident response, debugging stuck for roughly three hours, and transferring knowledge held by exactly one person. It does not pay off for routine CRUD work or sessions longer than about two hours.

How do I stop written disagreements from stalling a decision?▼

Apply the two-round rule: state the objection once with its cost and confidence, allow one response, then disagree-and-commit with a recorded revisit trigger, escalate to 15 minutes synchronous, or escalate to a named decider.

Why do RFC processes fail and how do I fix them?▼

RFCs fail from missing deadlines and missing deciders. A working process needs a comment deadline on the document, a single named decider rather than a committee, a size threshold so small changes skip the process, and an appended outcome section.

Related Skills

Explore More Software Engineering Skills→
thimsluggathimslugga

git-codebase-recon

Run git-based reconnaissance commands to surface codebase health signals.

Community
Advanced
3horizons3horizons

github-metrics

Collect engineering metrics from GitHub APIs and analyze PR cycle time.

Official
Advanced
d0whc3rd0whc3r
2

documentation-and-adrs

Record architectural decision rationale using a structured ADR template.

Community
Basic
devmuslimdevmuslim

Ceremonies

Guide agile and SAFe ceremonies with agendas, roles, and anti-patterns.

Community
Intermediate