wf-gardener

Audit design-docs and living docs for drift, broken links, and missing entries.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill wf-gardener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-gardener
Source: https://github.com/JSai23/claude-tooling/tree/main/compiled/wf/agentskills/wf-gardener
Command: npx skills add https://github.com/JSai23/claude-tooling --skill wf-gardener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining accurate, current design-docs and living docs is critical to prevent drift, broken links, and outdated decisions from hindering future work.

Core Features & Use Cases

  • Audit design-docs for freshness and truth against the current system.
  • Prune stale plans, update ARCHITECTURE.md and PRINCIPLES.md to reflect reality, and flag gaps or orphaned entries.
  • Verify cross-links and plan statuses to ensure consistency across repo documentation.

Quick Start

Audit and prune stale or drifting docs in design-docs/ and related living docs to restore alignment with the current system.

Frequently Asked Questions about wf-gardener

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

FAQPage Schema
How do I audit design-docs for drift and outdated entries?

To audit design-docs for drift, you can use this Skill to check living docs like ARCHITECTURE.md against the current system. It flags discrepancies, broken links, and orphaned entries, prompting updates to restore alignment.

What is the best way to maintain living docs and prevent documentation debt?

Maintaining living docs requires continuous pruning of stale plans and verifying cross-link consistency. This Skill enforces documentation health policies by identifying drift and prompting updates when reality and docs diverge.

How do I check ARCHITECTURE.md and PRINCIPLES.md for broken links and missing entries?

You can verify cross-links and plan statuses in ARCHITECTURE.md and PRINCIPLES.md by running a doc health audit. This process identifies broken links and missing entries, ensuring traceability to plans and system reality.

Can I use this to prune stale plans and update design-docs to reflect current reality?

Yes, you can prune stale plans and update design-docs to reflect reality. The Skill audits repository documentation, flags gaps or outdated decisions, and prompts for updates when discrepancies are found.

Why does my repository documentation have orphaned entries and how do I fix them?

Orphaned entries occur when living docs drift from the actual system architecture. You can fix them by auditing doc health to identify gaps, verifying plan statuses, and pruning outdated documentation to enforce consistency.

Does this doc health audit work without external dependencies?

Yes, the doc health audit works without external dependencies. It directly evaluates repository files like design-docs, ARCHITECTURE.md, and PRINCIPLES.md to trace discrepancies and enforce documentation policies independently.