docs-discover

Assess project documentation against codebase reality and propose updates.

3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/peel/fiddle --skill docs-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-discover
Source: https://github.com/peel/fiddle/tree/main/skills/docs-discover
Command: npx skills add https://github.com/peel/fiddle --skill docs-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and maintenance of essential project documentation, ensuring clarity and consistency across technical and product specifications.

Core Features & Use Cases

  • Socratic Dialogue: Engages users in a question-and-answer format to elicit detailed information for documentation.
  • Automated Doc Writing: Generates and updates documentation based on user input and codebase analysis.
  • Use Case: Kickstart a new project by using this Skill to generate the initial VISION, SYSTEM, and MARKET documents, ensuring all critical aspects are considered from the outset.

Quick Start

Use the docs-discover skill to review and update the VISION document for the current project.

Frequently Asked Questions about docs-discover

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

FAQPage Schema
What is Socratic dialogue for project documentation bootstrapping?

Socratic dialogue for project documentation uses a guided question-and-answer format to elicit detailed information, generating accurate VISION, SYSTEM, and MARKET documents from the outset.

How do I check if my existing project docs match the codebase reality?

To check existing project docs against codebase reality, use a documentation review process that identifies inconsistencies and proposes updates for VISION, SYSTEM, and RUNBOOKS, ensuring technical specifications align with codebase evolution.

What is the best way to generate initial technical writing for a new codebase?

The best way to generate initial technical writing for a new codebase is using an automated documentation bootstrapping tool that analyzes the codebase and engages you in dialogue to produce foundational VISION and SYSTEM documents.

Can I use automated docs generation for pricing and GTM strategy documents?

Yes, automated docs generation can produce and refine PRICING and GTM strategy documents. It assesses your project's evolution through guided dialogue and proposes updates to ensure these market-facing documents remain accurate.

What types of project documents should be reviewed periodically for consistency?

Project documents that should be reviewed periodically include VISION, MARKET, PRICING, GTM, SYSTEM, and RUNBOOKS. Regular reviews identify gaps and ensure documentation accuracy aligns with project evolution.

Does automated documentation generation work without an existing codebase?

Automated documentation generation can kickstart a new project by eliciting details through Socratic dialogue even before a full codebase exists, though codebase analysis is required to accurately assess existing documents and identify gaps later.