Stand: 2026-03-17

J01-83 72-10 CLI-Cache: erste Cache-V1 vorbereiten (Policy getrennt)
Type
Subtask
Status
Erledigt
Priority
Medium
Assignee
-
Sprint
-
Sprint role
-
Resolution
Fertig
Updated
2026-03-20T05:23:43.397+0100
Parent
J01-72

Contents key

This page

Canonical public work status for J01-83. This issue narrows the earlier, broader CLI-cache step down to a small, easily replaceable first cache iteration and explicitly separates the policy hardening into its own follow-up item.

Goal

Prepare a small cache V1 that gives humans and agents reliable recipes for recurring Jira work and makes those recipes an active skill-side building block, without prematurely pulling in the later security or curl hardening path.

Source and chronology basis

  • 2026-02-24: The J01 notes first recorded a CLI cache or recipe catalog as an intermediate step.
  • 2026-02-24: The system overview and ADR-0002 anchored that cache context publicly, but still mixed it with stronger policy language.
  • 2026-02-25 and 2026-02-26: The tagebuch refined the topic first as “cache vs. Codex skill” and then as “cache artefact vs. Codex skill”.
  • 2026-03-14: J01-95 provided the right pattern for this round: small local V1, quickly usable, replaceable later.
  • Negative finding: the exported docs/agile sources did not contain their own cache track, so this was not a missing leftover in J01-91/archive-topics.md.

Prepared now

  • narrowed J01-83 in Jira down to the cache V1
  • split the policy track into its own Jira candidate J01-101
  • added the new public work doc for J01-83
  • carried the source basis into the tagebuch as a dedicated search case and round note
  • implemented the first cache cell in the skill repo: shared-tooling/jira-pages/cache-recipes/parent-subtasks.md
  • corrected the goal of J01-83 toward active skill-side use of the cache path

First cache cell

The V1 is now implemented with one first small cache cell. That artefact covers the read case: read a Jira parent issue and derive the contained subtasks from it.

The copyable core command is:

atlassian jira http get "/rest/api/3/issue/<PARENT_KEY>?fields=subtasks,summary,status"

The recipe contains only the fields needed for this V1:

  • purpose
  • copyable command
  • placeholders
  • expected output fields
  • success signals
  • failure signals and limits

In V1, success means:

  • exit code 0
  • parseable JSON
  • a present fields.subtasks field
  • readable subtask fields key, fields.summary, fields.status.name

Active skill-side use

J01-83 does not stop at a stored example. All project skills that use recurring commands are expected to use the cache path actively:

  • look for a matching recipe first
  • add a missing recipe in the same work round
  • update an existing recipe when fields, paths, or expectations drift

The first cache cell is therefore the starting point and reference, not the full end state of the cache.

Explicitly not part of this V1:

  • saving the full response as a file
  • a local JSON snapshot cache
  • new CLI subcommands
  • new policy hardening in atlassian-http-client

V1 scope

  • exactly one first cache cell is enough for this iteration
  • that first recipe only describes: purpose, copyable command, placeholders, expected output fields, success signals, and limits
  • but this V1 already makes command-using project skills rely on the cache path shared-tooling/jira-pages/cache-recipes/
  • the solution stays intentionally small and quickly replaceable
  • the model is the V1 posture from J01-95, not its concrete feature set

Verification plan

Check Expectation Evidence / Location Status
First cache cell exists in the skill repo parent-subtasks.md exists and covers exactly one recurring read case shared-tooling/jira-pages/cache-recipes/parent-subtasks.md done
Command-using project skills treat the cache as the first search space koordination and jira-state-sync mention cache lookup and recipe upkeep explicitly project skill repo under skills/ done
Canonical public work doc is reachable directly from Jira Jira holds one remote link to /en/jira/issues/J01-83/; GitHub Pages keeps the DE/EN split Jira remote links for J01-83 done
Public Jira page shows the same closure state The public Jira area carries over status and public links from Jira without Jira Cloud links /en/jira/issues/J01-83/ done

Not part of J01-83

  • no broad recipe library
  • no mandatory snapshots
  • no new cache engine or persisted response store
  • no new policy hardening in atlassian-tools/curl
  • no new security or curl hardening as the DoD for this first iteration

Boundary to the policy track

  • J01-101 carries the separate policy follow-up work.
  • J01-83 remains the cache track and does not pull that policy work back into scope implicitly.