setup

Prepares a project's references documentation layer for agent workflow commands.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/ledtorch/coding-agent-workflow --skill setup-ledtorch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/ledtorch/coding-agent-workflow/tree/main/skills/setup
Command: npx skills add https://github.com/ledtorch/coding-agent-workflow --skill setup-ledtorch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After installing agent workflow commands into a project, the commands need a documentation layer (references/SKILL.md, conventions.md, architecture.md) to read from — this Skill either wires the commands into docs the project already has, or builds that layer from the real codebase. ## Core Features & Use Cases - Mode detection: Automatically detects adopt mode (project already has references/SKILL.md) versus init mode (no doc layer yet) without re-asking the user. - Adopt workflow: Maps existing docs to the three contract paths, then points, moves, or writes bridge docs without duplicating content. - Init workflow: Generates references/SKILL.md, architecture.md, conventions.md, and a feature-doc template, with every claim verified against actual files via ls or grep. - Use Case: After running install.sh in a new repository, run /setup so the agent reads your codebase and produces a verified routing index and conventions doc that /plan, /build, and /inspect can rely on. ## Quick Start Run /setup in your project right after install.sh and let the agent detect the mode and prepare the references documentation layer.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I set up agent workflow commands in an existing project?▼

Run install.sh from the workflow repository inside your project, then run /setup. The setup command detects whether your project already has references/SKILL.md and either wires the commands into your existing docs or builds the doc layer from your codebase.

What is the difference between adopt mode and init mode in project setup?▼

Adopt mode applies when the project already has a references/SKILL.md with real routing content; setup only bridges contract paths and proposes an edit. Init mode applies when no doc layer exists; setup writes the index, architecture, and conventions docs from verified codebase facts.

Can setup modify my source code or configuration files?▼

No. Setup writes only inside the references/ directory, plus one proposed diff to an existing references/SKILL.md that requires your approval. It never touches source, config, .gitignore, CI, or git history.

What happens if I skip running setup after install.sh?▼

The other commands still run from the codebase alone and say so at the top of each run. However, nothing gets checked against project conventions or architecture docs, and /plan and /inspect only use references/ as a working directory.

Why does setup refuse to overwrite files with the install.sh stub marker?▼

Files carrying the 'Stub from install.sh' marker have never been filled, so setup overwrites them freely. Any file without the marker is treated as user-authored and is only changed after showing a diff and receiving explicit approval.