alignlisted

# Align — Active Project Alignment DISCOVER → ASSESS → PLAN → IMPLEMENT → VERIFY → DOCUMENT. Creates files, configures structure, and implements practices. Unlike `/brana:onboard` (diagnostic, read-only), this skill actively builds. Replaces `/project-align` and `/venture-align`. ## When to use Initial setup of a new project, or when an existing project needs structural alignment. Run `/brana:onboard` first for the diagnostic — `/brana:align` implements what `/brana:onboard` finds. --- ## Step Registry On entry, create a CC Task step registry. Follow the [guided-execution protocol](../_shared/guided-execution.md). Register these steps: DISCOVER, ASSESS, PLAN, IMPLEMENT, VERIFY, DOCUMENT. **Plan mode:** Enter plan mode for DISCOVER and ASSESS (read-only diagnostic phases). Exit plan mode before IMPLEMENT. --- ## Phase 0: DISCOVER Before assessment, gather context. This shapes tier, CLAUDE.md content, and implementation depth. **Ask what can't be inferred. Skip what's obvious from the codebase.** ### Auto-detect project type Same detection as `/brana:onboard`: check for manifests (code) and venture dirs/keywords (venture). Classify as code, venture, or hybrid. ### Brainstorm / research repo detection (errata #154) Before applying the venture or code checklist, check for content-only repos: ```bash total=$(find . -not -path '*/.*' -type f | wc -l) md=$(find . -not -path '*/.*' -name '*.md' -type f | wc -l) has_src=$([ -d src ] && echo 1 || echo 0) has_manifest=