From 5474bb6578fa03abaa6b95b9be161e46a743bebb Mon Sep 17 00:00:00 2001 From: main Date: Fri, 20 Mar 2026 23:59:48 -0400 Subject: Move issues into state dir --- assets/codex-skills/jira-at-home/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'assets') diff --git a/assets/codex-skills/jira-at-home/SKILL.md b/assets/codex-skills/jira-at-home/SKILL.md index 541c7f7..be759d1 100644 --- a/assets/codex-skills/jira-at-home/SKILL.md +++ b/assets/codex-skills/jira-at-home/SKILL.md @@ -1,6 +1,6 @@ --- name: jira-at-home -description: Use when you want brutally basic per-project issue parking in this repository: bind a project, save a freeform note to `issues/.md`, list existing issue slugs, or read one issue back. Keep the workflow primitive; there are no issue types, statuses, or schema beyond slug plus Markdown body. +description: Use when you want brutally basic per-project issue parking without touching the worktree: bind a project, save a freeform note to the project’s state-backed `issues/.md`, list existing issue slugs, or read one issue back. Keep the workflow primitive; there are no issue types, statuses, or schema beyond slug plus Markdown body. --- -Bind the target project with `project.bind` before issue work unless the MCP was started with `--project`; then use `issue.save` to create or overwrite `issues/.md`, `issue.list` to enumerate the currently open issue files, and `issue.read` to recover one note body by slug. Treat the store as a tiny parked-ideas notebook, not a tracker: every issue is just freeform Markdown in the canonical `issues/` directory, and the only operational tools worth touching are `system.health` and `system.telemetry` when the transport itself looks suspect. +Bind the target project with `project.bind` before issue work unless the MCP was started with `--project`; then use `issue.save` to create or overwrite `issues/.md` under the project’s external state root, `issue.list` to enumerate the currently open issue files, and `issue.read` to recover one note body by slug. Treat the store as a tiny parked-ideas notebook, not a tracker: every issue is just freeform Markdown outside the repo in the canonical `issues/` directory for that project, and the only operational tools worth touching are `system.health` and `system.telemetry` when the transport itself looks suspect. -- cgit v1.2.3