Add Claude Code skill references to howtos and contributing guide

Author: max-svistunov

docs/contributing/howto-run-a-spike.md

@@ -4,6 +4,8 @@ A spike is a time-boxed research task that produces a design recommendation and
 proposed JIRAs.  This document describes how to run one in the Lightspeed Core
 project.
 
+**Claude Code shortcut**: `/spike` runs this process interactively.
+
 ## Outputs
 
 A spike produces:
@@ -149,6 +151,8 @@ Once all decisions are confirmed:
 1. Update the parent feature ticket description to point to the spec doc.
 2. File sub-JIRAs under the parent ticket using
    [jira-ticket-template.md](templates/jira-ticket-template.md).
+   Use `dev-tools/file-jiras.sh` to parse and file them from the spike doc
+   (Claude Code shortcut: `/file-jiras`).
 3. Each sub-JIRA's agentic tool instruction should point to the **spec doc**
    (not the spike doc), since the spec doc is the permanent reference.
 

docs/contributing/howto-write-a-spec-doc.md

@@ -4,6 +4,8 @@ A spec doc is the permanent in-repo feature specification.  It is the single
 source of truth for what the feature does and how it works.  All implementation
 JIRAs reference it.  Agentic coding tools read it for guidance.
 
+**Claude Code shortcut**: `/spec-doc` creates one interactively.
+
 ## When to write one
 
 - As part of a spike (see [howto-run-a-spike.md](howto-run-a-spike.md), step 6).

docs/contributing_guide.md

@@ -149,6 +149,10 @@ Templates for all of the above are in
 the spike, see
 [how to organize PoC output](contributing/howto-organize-poc-output.md).
 
+**Claude Code shortcuts**: `/spike`, `/spec-doc`, and `/file-jiras` automate
+parts of this process.  Use `dev-tools/file-jiras.sh` directly for JIRA filing
+without Claude Code.
+
 ## AI assistants
 
 ### “Mark” code with substantial AI-generated portions.