para-newlisted
Install: claude install-skill Vinedine/para-os
# Para new
Creates **one entity**: a project, an area, an idea, or a contact. Nothing else, with a single exception - a project or idea that would otherwise have nothing pointing at it also gets its counterparty's contact file ([references/scaffold.md](references/scaffold.md)). It also runs the one promotion the lifecycle defines, `resources/ideas/<name>/` to `projects/<name>/`, because a promoted idea is a created project whose brief already exists.
The first job is **classification, not scaffolding.** Most requests to "start a project" turn out to be an area, an idea, or a document that needs filing, and a vault that lets all of them land in `projects/` stops being readable. The sorting test runs before any question about the work itself.
**This skill is vault-agnostic.** It reads the vault's CLAUDE.md at runtime for the PARA layout, the sorting test as that vault words it, what a project means there, any declared brief shape, the action-marker syntax, the naming and language conventions, and the "do not add" list. No vault-specific paths are hardcoded.
Do NOT invoke to file an inbound document (`/para-triage` does that), to add an action to an entity that already exists (append to its `actions.md` directly), or to create the skeleton's standing subfolders: `areas/business/` and `areas/network/` ship with the vault and are not areas anyone creates.
## The sorting test
This skill's contract, and the vault's own rule: *committed and dated → project. Maintained, no end d