wiki-first-product-management

Organize project definition and architecture in the GitHub wiki.

Updated Apr 1, 2026

Search Tags:#architecture #documentation #governance #wiki #product-management #decision-records #project-goals

Ready to run

npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill wiki-first-product-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-first-product-management
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/wiki-first-product-management
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill wiki-first-product-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often rely on scattered notes, chat messages, and ad-hoc documents. This skill centralizes product definition and architectural rationale in the GitHub wiki, ensuring long-term visibility and alignment across teams.

Core Features & Use Cases

Put in the wiki: product definition
solution design
architecture and tradeoffs
project-level assumptions and rationale
decision records and clarifications
project goals and non-goals
Minimum documentation habit: when a decision changes behavior, update the relevant wiki page and link the page from the relevant issue or PR.
Spec ownership: Spec owns project-level assumptions; Spec keeps wiki content aligned with the intended product and the merged codebase; Builder should escalate project-wide ambiguity instead of inventing product truth

Quick Start

Create or update the wiki pages that contain project definition, architecture, and decision records, and link them to the relevant issues or PRs.

Frequently Asked Questions about wiki-first-product-management

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

FAQPage Schema

How do I store product scope and architecture decisions in a GitHub wiki?▼

Store product scope and architecture decisions in a GitHub wiki by centralizing project definitions, tradeoffs, and decision records as authoritative pages, then linking them from issues and PRs to ensure long-term alignment.

What is the minimum documentation habit for linking wiki decision records to issues?▼

The minimum documentation habit for wiki decision records requires updating the relevant wiki page when a decision changes behavior, then linking that page from the corresponding issue or PR to maintain context.

How do I manage project goals and assumptions across teams using wiki documentation?▼

Manage project goals and assumptions across teams using wiki documentation by capturing non-goals, rationale, and clarifications on dedicated wiki pages, making them the authoritative source for product context across lifecycles.

Can I use GitHub wiki pages as the authoritative source for product definition and design rationale?▼

Yes, you can use GitHub wiki pages as the authoritative source for product definition and design rationale by organizing project architecture and decision records there, requiring issues and PRs to link back for context.

What's the best way to centralize scattered product management notes and architecture tradeoffs?▼

The best way to centralize scattered product management notes and architecture tradeoffs is consolidating them into a GitHub wiki, establishing a single repository for product definition, design rationale, and decision records.