Tracker Write: $ARGUMENTS
Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor
write skill.
When the incoming description/body already contains the canonical ## Lisa Usage ledger, the vendor
writer must preserve that managed section on update and use the lisa-lisa-usage-accounting contract for any
body-vs-comment fallback. This shim only routes — it never edits tracker artifacts itself.
See the config-resolution rule for the full configuration schema and skill-mapping table.
Workflow
Resolve tracker config
Read .lisa.config.local.json first (if present), then .lisa.config.json. Local overrides global on a per-key basis. Use jq — never hand-parse JSON.
local_tracker=$(jq -r '.tracker // empty' .lisa.config.local.json 2>/dev/null)
global_tracker=$(jq -r '.tracker // empty' .lisa.config.json 2>/dev/null)
tracker="${local_tracker:-$global_tracker}"
Validate the value
- Missing / empty → stop and report:
"No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."
jira → confirm atlassian.cloudId and jira.project are present. If either is missing, stop and report: "tracker=jira but atlassian.cloudId and jira.project are not set in .lisa.config.json." Continue to Step 3a.
github → confirm github.org and github.repo are present. If either is missing, stop and report: "tracker=github but github.org and github.repo are not set in .lisa.config.json." Continue to Step 3b.
linear → confirm linear.workspace and linear.teamKey are present. If either is missing, stop and report: "tracker=linear but linear.workspace and linear.teamKey are not set in .lisa.config.json." Continue to Step 3c.
- Any other value → stop and report:
"Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."
Dispatch
- 3a (jira): Invoke
lisa-jira-write-ticket via the Skill tool, passing $ARGUMENTS verbatim.
- 3b (github): Invoke
lisa-github-write-issue via the Skill tool, passing $ARGUMENTS verbatim.
- 3c (linear): Invoke
lisa-linear-write-issue via the Skill tool, passing $ARGUMENTS verbatim.
Surface the vendor skill's output unchanged. Do not paraphrase; downstream callers parse the structured response.
Rules
- Never bypass dispatch — calling the vendor skill directly from a vendor-neutral caller defeats the per-project switch.
- Never drop, duplicate, or hand-rewrite an existing managed
## Lisa Usage section in this shim.
Writer-specific preservation logic belongs in the vendor writers and follows the
lisa-lisa-usage-accounting contract.
- Never accept a tracker value outside
{jira, github, linear}.
- Never mutate
$ARGUMENTS between layers. The vendor skills define their own input contract.
- Never inline gate logic here. All validation rules live in the vendor skills (
lisa-jira-validate-ticket / lisa-github-validate-issue / lisa-linear-validate-issue); this skill only routes.
- Readiness is the caller's explicit claim, not this shim's default. Per the
ready-role-filing rule, an omitted build_ready is not build-ready on every vendor, so a caller filing work it expects build-intake to pick up must pass build_ready: true, and a caller deliberately holding work outside the queue must pass a human_gate reason. This shim normalizes nothing — it forwards $ARGUMENTS verbatim and the vendor writers enforce the contract — which is exactly why the caller cannot rely on a vendor default here.
1---2name: lisa-tracker-write-33description: Vendor-neutral wrapper for…4---56# Tracker Write: $ARGUMENTS78Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor9write skill.1011When the incoming description/body already contains the canonical `## Lisa Usage` ledger, the vendor12writer must preserve that managed section on update and use the `lisa-lisa-usage-accounting` contract for any13body-vs-comment fallback. This shim only routes — it never edits tracker artifacts itself.1415See the `config-resolution` rule for the full configuration schema and skill-mapping table.1617## Workflow18191. **Resolve tracker config**2021 Read `.lisa.config.local.json` first (if present), then `.lisa.config.json`. Local overrides global on a per-key basis. Use `jq` — never hand-parse JSON.2223 ```bash24 local_tracker=$(jq -r '.tracker // empty' .lisa.config.local.json 2>/dev/null)25 global_tracker=$(jq -r '.tracker // empty' .lisa.config.json 2>/dev/null)26 tracker="${local_tracker:-$global_tracker}"27 ```28292. **Validate the value**3031 - Missing / empty → stop and report: `"No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."`32 - `jira` → confirm `atlassian.cloudId` and `jira.project` are present. If either is missing, stop and report: `"tracker=jira but atlassian.cloudId and jira.project are not set in .lisa.config.json."` Continue to Step 3a.33 - `github` → confirm `github.org` and `github.repo` are present. If either is missing, stop and report: `"tracker=github but github.org and github.repo are not set in .lisa.config.json."` Continue to Step 3b.34 - `linear` → confirm `linear.workspace` and `linear.teamKey` are present. If either is missing, stop and report: `"tracker=linear but linear.workspace and linear.teamKey are not set in .lisa.config.json."` Continue to Step 3c.35 - Any other value → stop and report: `"Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."`36373. **Dispatch**3839 - **3a (jira):** Invoke `lisa-jira-write-ticket` via the Skill tool, passing `$ARGUMENTS` verbatim.40 - **3b (github):** Invoke `lisa-github-write-issue` via the Skill tool, passing `$ARGUMENTS` verbatim.41 - **3c (linear):** Invoke `lisa-linear-write-issue` via the Skill tool, passing `$ARGUMENTS` verbatim.42434. **Surface the vendor skill's output unchanged.** Do not paraphrase; downstream callers parse the structured response.4445## Rules4647- Never bypass dispatch — calling the vendor skill directly from a vendor-neutral caller defeats the per-project switch.48- Never drop, duplicate, or hand-rewrite an existing managed `## Lisa Usage` section in this shim.49 Writer-specific preservation logic belongs in the vendor writers and follows the50 `lisa-lisa-usage-accounting` contract.51- Never accept a tracker value outside `{jira, github, linear}`.52- Never mutate `$ARGUMENTS` between layers. The vendor skills define their own input contract.53- Never inline gate logic here. All validation rules live in the vendor skills (`lisa-jira-validate-ticket` / `lisa-github-validate-issue` / `lisa-linear-validate-issue`); this skill only routes.54- **Readiness is the caller's explicit claim, not this shim's default.** Per the `ready-role-filing` rule, an omitted `build_ready` is **not build-ready** on every vendor, so a caller filing work it expects build-intake to pick up must pass `build_ready: true`, and a caller deliberately holding work outside the queue must pass a `human_gate` reason. This shim normalizes nothing — it forwards `$ARGUMENTS` verbatim and the vendor writers enforce the contract — which is exactly why the caller cannot rely on a vendor default here.