# Manage Tooling Documentation

> Establish or audit tooling stacks and documentation practices for product teams. Use this skill when a team's tools or documentation are creating friction or inefficiency.

- Skill: `alexe-ev/manage-tooling-documentation` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add alexe-ev/manage-tooling-documentation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexe-ev/manage-tooling-documentation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: alexe-ev (https://skillmd.com/u/alexe-ev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexe-ev/manage-tooling-documentation

---


# Manage Tooling & Documentation

## Purpose
Help teams select, configure, or audit their tooling stack and documentation practices to reduce friction and improve knowledge management.

## Skill type
Conceptual skill

## Use this skill when
- A team's tools are fragmented and creating knowledge silos
- Documentation doesn't exist, is outdated, or isn't used
- A new team needs to set up its tooling stack
- Tool consolidation is needed to reduce overhead

## Do not use this skill when
- The goal is process design for meetings (use design-operating-cadence)
- The goal is a technical infrastructure decision (use technical-product skills)

## Required inputs
- Current tooling landscape (even rough list)
- Team type and size
- Key documentation needs

## Optional inputs
- Pain points with current tools
- Budget constraints
- Cross-team tool dependencies

## Upstream context
Works best when:
- Team structure and operating cadence are defined
- Key workflows are mapped

## Downstream handoff
Output can feed:
- automate-workflow-governance
- align-cross-team-communication

## Instructions
1. Audit current tooling across: planning, documentation, communication, analytics, roadmapping.
2. Identify redundancies, gaps, and friction points.
3. Recommend a rationalized tooling stack.
4. Define documentation standards: where things live, naming conventions, update cadence.
5. Identify what should be documented but isn't.
6. Produce a documentation health assessment.

## Output
Provide:
- Current tooling audit
- Recommended tooling stack by category
- Documentation standards
- Documentation health assessment (what exists, what's missing, what's outdated)
- Recommended actions for immediate improvement
- Governance: who owns tool administration and documentation upkeep

## Risks / caveats
- Tool sprawl is a symptom of process problems, not the cause — fix the process first
- Documentation that isn't used is waste — design for findability and maintenance
- Avoid recommending major tooling changes without understanding migration cost