reportlisted

Generate a project status report for the project (`product_name`, Untype). The report covers: what was achieved, research conducted, current state, and what's next. ## Project configuration The manifest is this skill's configuration. If `$(git rev-parse --show-toplevel)/.claude/lifecycle-manifest.md` does not exist, the project has not adopted the kit: say so, offer to create it, and stop. Never infer the keys and run anyway. The kit ships the template as `lifecycle-manifest.template.md`; locate the installed copy with `find ~/.claude/plugins -path '*lifecycle-kit*' -name lifecycle-manifest.template.md | head -1`. The marketplace's `ADOPTING.md` carries a repo-inspecting setup prompt. Read `.claude/lifecycle-manifest.md` first (resolve via `$(git rev-parse --show-toplevel)/.claude/lifecycle-manifest.md`). Where a step names a manifest key in `code font` (`product_name`, `log_dir`, `log_archive`, `log_glob`, `log_pattern`, `research_dir`, `reports_dir`, `plan_doc`, `prose_gate`, `prose_rule`, `jargon_terms`), use that key's value. The plain-mode before/after examples are Untype-flavored illustrations of the technique, not configuration. ## Argument Parsing The user passes `$ARGUMENTS` which can be one of these forms (all optional — no argument means "everything"): **Audience flag (can appear anywhere in the arguments):** - `plain` — write the report for a non-technical audience (see Plain Mode below) - If `plain` is absent, produce the default developer-oriented report