skills.rest
tygwan
tygwanCOMMUNITY
Explore all skills by this author →
GitHub

dev-doc-system

Organize development documentation with structured templates for vision, decisions, and progress.

1|Updated Jan 9, 2026
Search Tags:#planning#development#documentation#retrospective#roadmap#ADR
One-click install
npx skills add https://github.com/tygwan/AgenticREVIT --skill dev-doc-system
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-doc-system
Source: https://github.com/tygwan/AgenticREVIT/tree/main/.claude/skills/dev-doc-system
Command: npx skills add https://github.com/tygwan/AgenticREVIT --skill dev-doc-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the fragmentation of development documentation by unifying direction, progress, decisions, backlog, and feedback into a single, structured system. It reduces manual handoffs and ensures that teams stay aligned with an auditable narrative of project evolution.

Core Features & Use Cases

  • Centralized documentation: maintains a single source of truth for vision, roadmap, decisions, status, changes, and retrospectives.
  • Structured templates: enforces consistent formats (VISION, ROADMAP, DECISIONS, CURRENT, CHANGELOG, RETRO, LEARNINGS, BACKLOG, ISSUES).
  • Workflow automation ready: integrates with automation pipelines to keep documents current and actionable across teams and projects.

Quick Start

Create your first vision document, then define a roadmap and backlog, capture key decisions, and log weekly progress to kick off the governance loop.

Frequently Asked Questions about dev-doc-system

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

FAQPage Schema
How do I set up unified documentation for tracking development direction and decisions?▼

Unified development documentation consolidates vision, roadmap, decisions, and progress into structured templates. Create a VISION document first, then define ROADMAP and BACKLOG, capture decisions with ADRs, and log progress weekly to establish a governance loop that keeps teams aligned.

What's the best way to organize development documentation across multiple teams and projects?▼

A centralized documentation system maintains a single source of truth using consistent frontmatter-driven templates for vision, decisions, status, and retrospectives. This structure reduces manual handoffs, enables automation integration, and creates an auditable narrative of project evolution across teams.

Can I automate development documentation updates in my workflow?▼

Yes. Structured templates with frontmatter support workflow automation pipelines to keep documentation current across teams. The system enables integration with automation tools to update roadmaps, changelogs, and retrospectives automatically.

How do I capture and track retrospectives and lessons learned in development?▼

Retrospective documentation uses structured templates to record feedback, learnings, and changes systematically. Dedicated RETRO and LEARNINGS formats ensure consistent capture and make retrospective data queryable for future project planning.

What problem does having separate documentation for roadmaps, decisions, and progress create?▼

Fragmented documentation across multiple systems creates misalignment, duplicated effort, and incomplete audit trails. A unified system consolidates roadmap, decisions, status, and feedback into one structured record, reducing handoffs and keeping teams on the same page.

Do I need existing documentation tools to start using development documentation governance?▼

No external dependencies required. The system works with basic structured templates and frontmatter entries. Teams can begin by creating vision and roadmap documents, then expand to decision logs and progress tracking at their own pace.

Related Skills

Explore More Content & Communication Skills→
scanadyscanady

tech-arch-architecture-decision-records

Create and index Architecture Decision Records using MADR and other templates.

Community
Advanced
gn-t-kgn-t-k

tech-article-writing

Guide technical-article writing through six phases using the Pyramid Principle and SCQA framework.

Community
Advanced
patmaddoxpatmaddox

plan

Synthesize Jujutsu commit history into structured org-mode project roadmaps.

Community
Advanced
MisonLMisonL
8

architecture

Document architectural decisions with structured templates, checklists, and frontmatter-driven records.

Community
Advanced