specs

Discover repository topology and bootstrap AGENTS.md and specs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/scripness/skills --skill specs-scripness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specs
Source: https://github.com/scripness/skills/tree/main/src/specs
Command: npx skills add https://github.com/scripness/skills --skill specs-scripness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Bootstrap, sync, or repair the repo truth layer for AGENTS.md and specs when guidance is missing, outdated, or unsafe for planning and execution.

Core Features & Use Cases

  • Discover actual repo topology and owning paths (apps, packages, services, docs).
  • Bootstrap minimal AGENTS.md and specs/ when absent or stale.
  • Sync and repair root repo-truth documents to align with code reality, while excluding generated, vendor, or noise paths.
  • Support gap-close workflows to resolve repo-truth gaps that block safe planning, execution, or verification.

Quick Start

Run the repo-truth bootstrap flow to generate minimal AGENTS.md and specs/ that reflect the current project topology.

Frequently Asked Questions about specs

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

FAQPage Schema
How do I bootstrap AGENTS.md and specs for an existing repository?

To bootstrap AGENTS.md and specs, the tool discovers the repository's actual topology and generates minimal repo-truth documents that reflect current project owning paths and boundaries.

What is the best way to sync AGENTS.md with code reality?

Syncing AGENTS.md with code reality involves applying repair workflows to align root repo-truth documents with actual code structure, while explicitly excluding generated, vendor, and copied-artifact noise paths.

How do I repair outdated repository specs that block safe planning?

Repairing outdated repository specs uses gap-close workflows to resolve repo-truth gaps, ensuring durable and navigable guidance that matches code reality for safe execution and verification.

When should I use a gap-close workflow for repo truth documents?

Use a gap-close workflow for repo truth documents when missing or unsafe AGENTS.md guidance blocks safe planning, execution, or verification, requiring topology alignment to restore navigable project boundaries.

Can I exclude vendor and generated directories when syncing repository topology?

Yes, syncing repository topology automatically excludes generated, vendor, and copied-artifact noise paths to ensure the repo-truth layer accurately defines owning paths and maintenance boundaries without false positives.

Does the specs bootstrap workflow support multi-package repository topologies?

Yes, the bootstrap workflow identifies actual repository topology across apps, packages, services, and docs, generating minimal AGENTS.md and specs that define clear owning paths for multi-package environments.