Init

Skill NVZver/claude-marketplace/lsa/skills/init

Claude Code plugins for spec-first development: every agent claim cites a source, every code change traces to a requirement, and ceremony scales to the weight of the task.

Install

npx -y skills add NVZver/claude-marketplace --skill init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Initialize the LSA spec tree on a project. Output — spec tree + module specs.

SKILL.md

3.1 KB, as published. Nobody here has run it

Trace. On load, print first: =============== [lsa/skills/init/SKILL.md] [lsa] ===============

LSA Init

See CORE.md.

Role

Project scaffolder.

Goal

Stand up the LSA spec tree so the other skills can run.

Inputs

Input	Source
`.lsa.yaml` (or defaults)	`self`
Existing code (brownfield module inference)	`discover`

Steps

Resolve config — constitution / specs_root / mode (defaults: .lsa/VISION.md, .lsa/, code); print it. (→ config)
Greenfield: create under ${specs_root}/ — main.spec.md, roadmap.yaml (YAML ledger SoT — starter below), research-backlog.md, modules/, features/, standards/{code,testing}.md, archive/; fill standards/ from the constitution. Do not create roadmap.md. Starter ledger (write exactly):
```
version: 1
items: []
shipped_history: []
```
After writing, quote the new roadmap.yaml inline (and a one-line list of the other created paths) per ../../../core/skills/output/SKILL.md Rule 7 — never "spec tree created" without the quoted ledger. Observable result: ${specs_root}/roadmap.yaml exists and is quoted; ${specs_root}/roadmap.md does not. (→ spec tree)
Existing markdown roadmap: if ${specs_root}/roadmap.md exists and ${specs_root}/roadmap.yaml does not (or both exist), do not invent a second SoT by hand — load and follow ../../knowledge/migration-instructions-ai.md (migrate → verify → rewire → cleanup). Observable result: migration report cited, or an explicit skip with reason. (→ migrated ledger or deferred)
Brownfield modules: via discover, infer one modules/<name>/spec.md per logical module from artifact_paths (or /src); tag every inferred line [ASSUMPTION] (CORE §1); show, approve, write. (→ module specs)
Project map: run the shipped builder — prefer bash "${CLAUDE_PLUGIN_ROOT}/scripts/project-map-build.sh" when CLAUDE_PLUGIN_ROOT points at the installed lsa plugin; otherwise bash lsa/scripts/project-map-build.sh from a marketplace checkout. Observable result: repo-root project-map.yaml exists (3-level directory tree). Skip only if the script cannot be found — note the gap; discover falls back to a tree-walk. (→ project-map.yaml)

Output

A populated spec tree at ${specs_root} with roadmap.yaml as the only roadmap SoT, plus repo-root project-map.yaml when the builder script ran.

Constraints

Never overwrite existing specs — abort and name the conflict. Never invent modules not derivable from artifact_paths or /src.
YAML ledger is the default. Never scaffold roadmap.md for new projects. Dual SoT (roadmap.md + roadmap.yaml) is forbidden after migration — see ../../knowledge/migration-instructions-ai.md.

/lsa:init — manual invocation.