LCORE-1576: Document feature design process: howtos, templates, skills & CLI tool

.claude/commands/file-jiras.md

@@ -0,0 +1,26 @@
+Parse proposed JIRAs from a spike doc and file them via the Jira API
+
+You are filing JIRA sub-tickets for a Lightspeed Core feature.
+
+The user will provide either a spike doc path or tell you which feature's
+JIRAs to file.  They will also provide the parent JIRA ticket number.
+
+## Credentials
+
+Jira credentials must be in `~/.config/jira/credentials.json`.  If this file
+doesn't exist, tell the user to create it (see `dev-tools/file-jiras.sh` for
+the format and instructions).
+
+## Process
+
+1. Run `dev-tools/file-jiras.sh <spike-doc.md> <parent-ticket>` with
+   `echo "quit"` piped in, so it parses and exits without filing.
+
+2. Read every file in `/tmp/jiras/`.  For each, verify:
+   - Content matches the corresponding section in the spike doc (no truncation,
+     no extra content swallowed from subsequent sections).
+
+3. Report any issues to the user.  If all files look correct, tell the user
+   to run the script interactively — provide the full command including `cd`
+   to the repository root:
+   `cd <repo-path> && sh dev-tools/file-jiras.sh <spike-doc.md> <parent-ticket>`

.claude/commands/spec-doc.md

@@ -0,0 +1,12 @@
+Create a feature spec doc with requirements, architecture, and implementation guide
+
+You are creating a feature spec doc for the Lightspeed Core project.
+
+Follow the guidance in `docs/contributing/howto-write-a-spec-doc.md`.  Use
+`docs/contributing/templates/spec-doc-template.md` as the starting point.
+
+The user will provide context about the feature — a spike doc, a description,
+or a conversation.  Read what is provided and ask for anything missing.
+
+Place the spec doc at `docs/design/<feature>/<feature>.md`.  Confirm the
+feature name and path with the user.

.claude/commands/spike.md

@@ -0,0 +1,12 @@
+Run a design spike: research, PoC, decisions, and proposed JIRAs
+
+You are starting a spike for a feature in the Lightspeed Core project.
+
+Follow the process in `docs/contributing/howto-run-a-spike.md`.  Use the
+templates it references.
+
+The user will provide context about the feature — a JIRA ticket, a description,
+or a conversation.  Read what is provided and ask for anything missing.
+
+At decision points, present what you've found and ask the user before proceeding.
+The user makes the decisions — you assist with the research and documenting.