alexe-ev 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
- Audit current tooling across: planning, documentation, communication, analytics, roadmapping.
- Identify redundancies, gaps, and friction points.
- Recommend a rationalized tooling stack.
- Define documentation standards: where things live, naming conventions, update cadence.
- Identify what should be documented but isn't.
- 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