Doc Requirements Matrix

Framework for capturing documentation requirements, scoring priority, and assigning owners.

Published by @gtmagents·from gtmagents/gtm-agents·0 agent reads / 30d·0 saves·Updated June 14, 2026

Doc Requirements Matrix Skill

When to Use

Intake from product, engineering, support, or compliance teams.
Prioritizing doc requests against limited capacity.
Tracking readiness requirements for launches or audits.

Framework

Request Intake – requester, audience, format, deadline, status, linked release.
Scoring Criteria – impact, urgency, compliance, audience reach, reuse potential.
Dependencies – SMEs, assets, tooling, localization, approvals.
Status Tracking – backlog → in progress → review → published → refresh queued.
Reporting – dashboards for open requests, SLA breaches, and effort allocation.

Templates

Requirement intake form (Notion/Sheet) with scoring formula.
Priority board with filters for audience, format, product area.
Weekly review agenda highlighting top priorities + blockers.

Tips

Align scoring weights with leadership priorities each quarter.
Attach spec links, mockups, and SME contacts to reduce back-and-forth.
Pair with plan-documentation-roadmap to auto-populate backlog sections.

More on the bench

Product Launch Checklist

Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch monitoring.

product-management+1

Launch Readiness

Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.

product-management+2

Iso42001 Specialist

ISO/IEC 42001:2023 AI Management System (AIMS) specialist for compliance teams running internal audits. Three decisions: (1) Where are the gaps against Clauses 4-10 and what do we close first? (2) What goes in the AI risk register and which Annex A controls treat each risk? (3) What's the 12-month internal audit plan that satisfies Clause 9.2? Use when preparing for certification, scoping internal audit cycles, or onboarding AI systems into an existing ISMS (27001) / QMS (13485) program. NOT an executive AI strategy skill (see chief-ai-officer-advisor). NOT EU AI Act compliance (see compliance-team-eu-ai-act).

Alireza Rezvani

Sharebench · Public bench

Connect via MCP.

Add the public bench to any AI tool. Your agents read every artifact you see — no signup needed.

1Pick your tool

# Add the public bench as an MCP server
claude mcp add --transport http sharebench-public https://mcp-public.sharebench.ai

# Settings → MCP → Add new MCP server
{
  "mcpServers": {
    "sharebench-public": {
      "url": "https://mcp-public.sharebench.ai"
    }
  }
}

# Custom GPT or Developer Mode
# Add a remote MCP connector with this URL:
https://mcp-public.sharebench.ai

# Append to ~/.codex/config.toml
[mcp_servers.sharebench_public]
url = "https://mcp-public.sharebench.ai"

2Ask your agent for an artifact

Once connected, just ask in plain language — your agent searches the bench and pulls in what it needs.“Pull the brand voice from sharebench and rewrite this draft.”