docs-manager

Centralize project documentation into a single main guide with YAML frontmatter.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/gaurangrshah/gsc-plugins --skill docs-manager-gaurangrshah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-manager
Source: https://github.com/gaurangrshah/gsc-plugins/tree/main/plugins/docs/skills/docs-manager
Command: npx skills add https://github.com/gaurangrshah/gsc-plugins --skill docs-manager-gaurangrshah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered project documentation into a single main guide, enabling inline updates and consistent knowledge through journal reconciliation and a shared worklog database.

Core Features & Use Cases

  • Inline updates: Update the main guide inline as changes happen, ensuring the primary source stays current.
  • Journal reconciliation: Convert task journals into structured decisions and learnings for long-term reference.
  • Knowledge persistence: Publish reusable patterns and decisions to a centralized worklog database for cross-project reuse.
  • Use Case: A team completes a sprint and reconciles journal notes into decisions, guides, and knowledge entries for onboarding and future work.

Quick Start

Open the main guide and update the relevant inline documentation to reflect the latest changes.

Frequently Asked Questions about docs-manager

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

FAQPage Schema
How do I prevent documentation drift across multiple projects?

To prevent documentation drift, you consolidate scattered project documentation into a single source of truth and apply inline updates as changes happen, ensuring the primary guide stays current.

What is the best way to manage inline updates for a living knowledge base?

Managing a living knowledge base involves updating the main guide inline directly as changes occur, which keeps the primary documentation source current without needing separate sync workflows.

How does journal reconciliation work for task journals and learnings?

Journal reconciliation works by converting task journals into structured decisions and learnings, transferring temporary notes into long-term reference material for onboarding and future work.

Do I need YAML frontmatter to maintain inline guides and worklogs?

Yes, you need YAML frontmatter in new docs to maintain inline guides and worklogs, as it provides the required structured metadata for the single-source documentation workflow.

Can I publish reusable patterns to a centralized worklog database for cross-project knowledge sharing?

Yes, you can publish reusable patterns and decisions to a centralized worklog database, enabling cross-project knowledge sharing and persistent learning across teams.

When should I not use a single-source documentation approach for team guides?

You should avoid a single-source documentation approach if your team cannot commit to reconciling task journals into structured guides or lacks the need for cross-project knowledge persistence.