lldlisted

Generate a Low Level Design (LLD) document from a freeform description and write it to a markdown file. $ARGUMENTS may include: - A freeform description of the feature, component, or system, or - `--hld <path>` followed by an optional extra description (e.g. `/lld --hld design/hld-user-auth.md focus on the token refresh flow`). When `--hld` is provided, read the file at `<path>` and use its content as the primary source of context. The extra description, if present, narrows the scope. - `--mode living|strict` — sets the doc's `Mode`. If `--hld` was provided and `--mode` was not, inherit the HLD's `Mode` field. Otherwise defaults to `strict`. - `--amend [path] <change description>` — targeted edit to an existing doc's `## Requirements` section only. `<path>` may be omitted if it's already clear from this conversation — see the Amend Mode steps below, which are skipped entirely when this flag isn't present. If $ARGUMENTS is empty, ask the user to provide a description or an HLD path and stop. ### Normal generation 1. Parse $ARGUMENTS. If `--hld <path>` is present, read the file at `<path>`. Use the HLD content (plus any extra description) as the source for all sections below. If the path does not exist, tell the user and stop. If no `--hld` flag is present, use $ARGUMENTS as the description directly. 1. Derive a filename slug from the description or HLD title: lowercase, replace spaces and special characters with hyphens, truncate to ~5 words, and prefix with `lld-` (e.g.