ariadne

Generates and maintains Vision, architecture, PRD, execution-plan milestone maps, and AGENTS.md for software projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ariadne provides a documentation-first, milestone-driven method for starting and evolving long-lived software projects while keeping the project’s operating manual (AGENTS.md) lean and synchronized with the repo’s branching and status.

Core Features & Use Cases

  • Scaffold new projects end-to-end: project profile, vision/strategy, master PRD + architecture, roadmap, capability mini-PRDs, execution plan, and AGENTS.md.
  • Operate existing scaffolded projects with a continuous thread: intake ritual, next-best-action guidance, ripple-effect edits, and milestone close workflows.
  • Enforce nested trunk-based branching: each milestone lives on its own milestone/<id>-<slug> branch, close-milestone merges are the merge gate, and recovery/abandon/pivot patterns are standardized.
  • Keep decisions disciplined: locked decisions (D-N), open architectural decisions (OAD-N), and status updates propagate via an explicit ripple matrix.

Quick Start

Say: ariadne, scaffold a new project, and answer the phase-0 project profile questions to generate the full documentation foundation and AGENTS.md.

Frequently Asked Questions about ariadne

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

FAQPage Schema
How do I scaffold documentation for a new long-lived software project from scratch?

To scaffold project documentation, you initiate phase-0 project profile questions to generate a full documentation foundation including vision, PRD, architecture, capability specs, an execution-plan milestone map, and a lean AGENTS.md operating manual.

What is the best way to keep an AGENTS.md operating manual synchronized with project status and branching?

Keeping AGENTS.md synchronized involves using a documentation-first methodology with explicit ripple-effect edits and a ripple matrix that propagates status updates, locked decisions, and milestone advancements across dependent project documents.

How does nested milestone branching work for trunk-based project operations?

Nested milestone branching places each milestone on its own branch, using close-milestone merges as the merge gate and applying standardized recovery, abandon, or pivot patterns to maintain strict trunk-based operational discipline.

Can I retrofit an existing repository with milestone planning and execution-plan documentation?

Yes, you can retrofit an existing repository by applying a documentation-first methodology to generate a master PRD, architecture, roadmap, capability mini-PRDs, and an AGENTS.md file to establish continuous project operations.

How do ripple-effect updates work when architectural decisions change in a long-lived project?

Ripple-effect updates propagate changes across dependent documents by using an explicit ripple matrix to ensure locked decisions and open architectural decisions stay consistent throughout capability specs and the execution plan.

When should I not use a documentation-first milestone-driven approach for project operations?

You should avoid documentation-first milestone-driven project operations if your work lacks long-lived lifecycle requirements, as the overhead of maintaining an AGENTS.md manual, ripple matrix, and nested branching offers little value for short-term tasks.