jorgex-stack 1.0.1 → 1.0.2

package/stack/skills/to-issues/SKILL.md

@@ -1,83 +1,83 @@
----
-name: to-issues
-description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
----
-
-# To Issues
-
-Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-### 1. Gather context
-
-Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
-
-### 2. Explore the codebase (optional)
-
-If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
-
-### 3. Draft vertical slices
-
-Break the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
-
-Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
-
-<vertical-slice-rules>
-- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
-- A completed slice is demoable or verifiable on its own
-- Prefer many thin slices over few thick ones
-</vertical-slice-rules>
-
-### 4. Quiz the user
-
-Present the proposed breakdown as a numbered list. For each slice, show:
-
-- **Title**: short descriptive name
-- **Type**: HITL / AFK
-- **Blocked by**: which other slices (if any) must complete first
-- **User stories covered**: which user stories this addresses (if the source material has them)
-
-Ask the user:
-
-- Does the granularity feel right? (too coarse / too fine)
-- Are the dependency relationships correct?
-- Should any slices be merged or split further?
-- Are the correct slices marked as HITL and AFK?
-
-Iterate until the user approves the breakdown.
-
-### 5. Publish the issues to the issue tracker
-
-For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
-
-Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
-
-<issue-template>
-## Parent
-
-A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
-
-## What to build
-
-A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
-
-Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Acceptance criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2
-- [ ] Criterion 3
-
-## Blocked by
-
-- A reference to the blocking ticket (if any)
-
-Or "None - can start immediately" if no blockers.
-
-</issue-template>
-
-Do NOT close or modify any parent issue.
+---
+name: to-issues
+description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
+---
+
+# To Issues
+
+Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
+
+The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
+
+## Process
+
+### 1. Gather context
+
+Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
+
+### 2. Explore the codebase (optional)
+
+If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
+
+### 3. Draft vertical slices
+
+Break the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
+
+Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
+
+<vertical-slice-rules>
+- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
+- A completed slice is demoable or verifiable on its own
+- Prefer many thin slices over few thick ones
+</vertical-slice-rules>
+
+### 4. Quiz the user
+
+Present the proposed breakdown as a numbered list. For each slice, show:
+
+- **Title**: short descriptive name
+- **Type**: HITL / AFK
+- **Blocked by**: which other slices (if any) must complete first
+- **User stories covered**: which user stories this addresses (if the source material has them)
+
+Ask the user:
+
+- Does the granularity feel right? (too coarse / too fine)
+- Are the dependency relationships correct?
+- Should any slices be merged or split further?
+- Are the correct slices marked as HITL and AFK?
+
+Iterate until the user approves the breakdown.
+
+### 5. Publish the issues to the issue tracker
+
+For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
+
+Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
+
+<issue-template>
+## Parent
+
+A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
+
+## What to build
+
+A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
+
+Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
+
+## Acceptance criteria
+
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+## Blocked by
+
+- A reference to the blocking ticket (if any)
+
+Or "None - can start immediately" if no blockers.
+
+</issue-template>
+
+Do NOT close or modify any parent issue.

package/stack/skills/to-prd/SKILL.md

@@ -1,72 +1,72 @@
----
-name: to-prd
-description: Turn the current conversation context into a PRD at work/{name}/PRD.md (work-lifecycle flow). Use when user wants to create a PRD from the current context.
----
-
-This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
-
-## Process
-
-1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
-
-2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can.
-
-Check with the user that these seams match their expectations.
-
-3. Write the PRD using the template below to `work/{name}/PRD.md`, where `{name}` is the work's canonical kebab-case name (see the `work-lifecycle` skill) — the human reviews it there. Exception: if the project manages its work through an issue tracker and the user wants the PRD there, publish it to the tracker instead and apply the `ready-for-agent` triage label — no need for additional triage.
-
-<prd-template>
-
-## Problem Statement
-
-The problem that the user is facing, from the user's perspective.
-
-## Solution
-
-The solution to the problem, from the user's perspective.
-
-## User Stories
-
-A LONG, numbered list of user stories. Each user story should be in the format of:
-
-1. As an <actor>, I want a <feature>, so that <benefit>
-
-<user-story-example>
-1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
-</user-story-example>
-
-This list of user stories should be extremely extensive and cover all aspects of the feature.
-
-## Implementation Decisions
-
-A list of implementation decisions that were made. This can include:
-
-- The modules that will be built/modified
-- The interfaces of those modules that will be modified
-- Technical clarifications from the developer
-- Architectural decisions
-- Schema changes
-- API contracts
-- Specific interactions
-
-Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
-
-Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Testing Decisions
-
-A list of testing decisions that were made. Include:
-
-- A description of what makes a good test (only test external behavior, not implementation details)
-- Which modules will be tested
-- Prior art for the tests (i.e. similar types of tests in the codebase)
-
-## Out of Scope
-
-A description of the things that are out of scope for this PRD.
-
-## Further Notes
-
-Any further notes about the feature.
-
-</prd-template>
+---
+name: to-prd
+description: Turn the current conversation context into a PRD at work/{name}/PRD.md (work-lifecycle flow). Use when user wants to create a PRD from the current context.
+---
+
+This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
+
+## Process
+
+1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
+
+2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can.
+
+Check with the user that these seams match their expectations.
+
+3. Write the PRD using the template below to `work/{name}/PRD.md`, where `{name}` is the work's canonical kebab-case name (see the `work-lifecycle` skill) — the human reviews it there. Exception: if the project manages its work through an issue tracker and the user wants the PRD there, publish it to the tracker instead and apply the `ready-for-agent` triage label — no need for additional triage.
+
+<prd-template>
+
+## Problem Statement
+
+The problem that the user is facing, from the user's perspective.
+
+## Solution
+
+The solution to the problem, from the user's perspective.
+
+## User Stories
+
+A LONG, numbered list of user stories. Each user story should be in the format of:
+
+1. As an <actor>, I want a <feature>, so that <benefit>
+
+<user-story-example>
+1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
+</user-story-example>
+
+This list of user stories should be extremely extensive and cover all aspects of the feature.
+
+## Implementation Decisions
+
+A list of implementation decisions that were made. This can include:
+
+- The modules that will be built/modified
+- The interfaces of those modules that will be modified
+- Technical clarifications from the developer
+- Architectural decisions
+- Schema changes
+- API contracts
+- Specific interactions
+
+Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
+
+Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
+
+## Testing Decisions
+
+A list of testing decisions that were made. Include:
+
+- A description of what makes a good test (only test external behavior, not implementation details)
+- Which modules will be tested
+- Prior art for the tests (i.e. similar types of tests in the codebase)
+
+## Out of Scope
+
+A description of the things that are out of scope for this PRD.
+
+## Further Notes
+
+Any further notes about the feature.
+
+</prd-template>

package/upstreams.json

@@ -1,96 +1,96 @@
-{
-  "$comment": "Terceros gestionados por `jorgex-stack update`: fuente, versión conocida y política. `commit` = pin del upstream en la última revisión aceptada (2026-06-11, auditoría de seguridad): update --check compara el HEAD del repo contra el pin y avisa si se movió; cualquier actualización de la copia vendorizada se hace con diff manual y re-pin deliberado, nunca a ciegas. El pin es del repo completo (no por path): en monorepos activos un pin movido no implica que la skill cambiara — el diff lo confirma. Las skills 'modified: true' tienen cambios locales respecto al upstream — update debe hacer diff/aviso, NUNCA reemplazo ciego (PRD §7.3). Skills propias sin upstream (no se actualizan desde fuera): agent-delegation, work-lifecycle. `path` = ruta dentro del repo upstream donde vive la skill (para diff/descarga quirúrgica). `kind: \"release\"` = la actualización se compara contra tags de release en vez de HEAD (e.g. paquetes Python sin SKILL.md en repo).",
-  "tools": {
-    "engram": {
-      "kind": "binary",
-      "source": "github:Gentleman-Programming/engram",
-      "verify": "sha256",
-      "policy": "respect-existing — D7: si hay un Engram instalado (binario o DB), no se toca; update del binario solo con confirmación explícita y la DB jamás"
-    }
-  },
-  "skills": {
-    "agent-browser": {
-      "source": "github:vercel-labs/agent-browser",
-      "path": "skills/agent-browser",
-      "commit": "5185339ca3fdab9848e11b8ec676eecfdec3733f"
-    },
-    "deploy-to-vercel": {
-      "source": "github:vercel-labs/agent-skills",
-      "path": "skills/deploy-to-vercel",
-      "version": "3.0.0",
-      "commit": "f8a72b9603728bb92a217a879b7e62e43ad76c81",
-      "note": "por diseño empaqueta el proyecto entero (tarball) y lo sube a un endpoint de Vercel para desplegarlo; excluye .env/.env.*/.git/node_modules"
-    },
-    "diagnose": {
-      "source": "github:mattpocock/skills",
-      "path": "skills/engineering/diagnose",
-      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
-    },
-    "find-skills": {
-      "source": "github:vercel-labs/skills",
-      "path": "skills/find-skills",
-      "commit": "be0dd25b4a8665894a56f45ef582cc02ca802c39"
-    },
-    "graphify": {
-      "source": "github:safishamsi/graphify",
-      "kind": "release",
-      "version": "0.7.16",
-      "commit": "cce26730212baab6d92ce5f390ef5aae56268f31"
-    },
-    "mcp-builder": {
-      "source": "github:anthropics/skills",
-      "path": "skills/mcp-builder",
-      "commit": "57546260929473d4e0d1c1bb75297be2fdfa1949",
-      "license": "Apache-2.0"
-    },
-    "obsidian-cli": {
-      "source": "github:kepano/obsidian-skills",
-      "path": "skills/obsidian-cli",
-      "commit": "a1dc48e68138490d522c04cbf5822214c6eb1202"
-    },
-    "obsidian-markdown": {
-      "source": "github:kepano/obsidian-skills",
-      "path": "skills/obsidian-markdown",
-      "commit": "a1dc48e68138490d522c04cbf5822214c6eb1202"
-    },
-    "react-doctor": {
-      "source": "github:millionco/react-doctor",
-      "path": "skills/react-doctor",
-      "commit": "a48fb06ffbe7221655e18529fcc954ecae17a22f"
-    },
-    "skill-creator": {
-      "source": "github:anthropics/skills",
-      "path": "skills/skill-creator",
-      "commit": "57546260929473d4e0d1c1bb75297be2fdfa1949",
-      "license": "Apache-2.0"
-    },
-    "supabase": {
-      "source": "github:supabase/agent-skills",
-      "path": "skills/supabase",
-      "version": "0.1.2",
-      "commit": "1356046015476711a769601079262b5635929427"
-    },
-    "supabase-postgres-best-practices": {
-      "source": "github:supabase/agent-skills",
-      "path": "skills/supabase-postgres-best-practices",
-      "commit": "1356046015476711a769601079262b5635929427",
-      "license": "MIT"
-    },
-    "tdd": {
-      "source": "github:mattpocock/skills",
-      "path": "skills/engineering/tdd",
-      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
-    },
-    "to-issues": {
-      "source": "github:mattpocock/skills",
-      "path": "skills/engineering/to-issues",
-      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
-    },
-    "to-prd": {
-      "source": "github:mattpocock/skills",
-      "path": "skills/engineering/to-prd",
-      "commit": "694fa30311e02c2639942308513555e61ee84a6f",
-      "modified": true
-    }
-  }
-}
+{
+  "$comment": "Terceros gestionados por `jorgex-stack update`: fuente, versión conocida y política. `commit` = pin del upstream en la última revisión aceptada (2026-06-11, auditoría de seguridad): update --check compara el HEAD del repo contra el pin y avisa si se movió; cualquier actualización de la copia vendorizada se hace con diff manual y re-pin deliberado, nunca a ciegas. El pin es del repo completo (no por path): en monorepos activos un pin movido no implica que la skill cambiara — el diff lo confirma. Las skills 'modified: true' tienen cambios locales respecto al upstream — update debe hacer diff/aviso, NUNCA reemplazo ciego (PRD §7.3). Skills propias sin upstream (no se actualizan desde fuera): agent-delegation, work-lifecycle. `path` = ruta dentro del repo upstream donde vive la skill (para diff/descarga quirúrgica). `kind: \"release\"` = la actualización se compara contra tags de release en vez de HEAD (e.g. paquetes Python sin SKILL.md en repo).",
+  "tools": {
+    "engram": {
+      "kind": "binary",
+      "source": "github:Gentleman-Programming/engram",
+      "verify": "sha256",
+      "policy": "respect-existing — D7: si hay un Engram instalado (binario o DB), no se toca; update del binario solo con confirmación explícita y la DB jamás"
+    }
+  },
+  "skills": {
+    "agent-browser": {
+      "source": "github:vercel-labs/agent-browser",
+      "path": "skills/agent-browser",
+      "commit": "5185339ca3fdab9848e11b8ec676eecfdec3733f"
+    },
+    "deploy-to-vercel": {
+      "source": "github:vercel-labs/agent-skills",
+      "path": "skills/deploy-to-vercel",
+      "version": "3.0.0",
+      "commit": "f8a72b9603728bb92a217a879b7e62e43ad76c81",
+      "note": "por diseño empaqueta el proyecto entero (tarball) y lo sube a un endpoint de Vercel para desplegarlo; excluye .env/.env.*/.git/node_modules"
+    },
+    "diagnose": {
+      "source": "github:mattpocock/skills",
+      "path": "skills/engineering/diagnose",
+      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
+    },
+    "find-skills": {
+      "source": "github:vercel-labs/skills",
+      "path": "skills/find-skills",
+      "commit": "be0dd25b4a8665894a56f45ef582cc02ca802c39"
+    },
+    "graphify": {
+      "source": "github:safishamsi/graphify",
+      "kind": "release",
+      "version": "0.7.16",
+      "commit": "cce26730212baab6d92ce5f390ef5aae56268f31"
+    },
+    "mcp-builder": {
+      "source": "github:anthropics/skills",
+      "path": "skills/mcp-builder",
+      "commit": "57546260929473d4e0d1c1bb75297be2fdfa1949",
+      "license": "Apache-2.0"
+    },
+    "obsidian-cli": {
+      "source": "github:kepano/obsidian-skills",
+      "path": "skills/obsidian-cli",
+      "commit": "a1dc48e68138490d522c04cbf5822214c6eb1202"
+    },
+    "obsidian-markdown": {
+      "source": "github:kepano/obsidian-skills",
+      "path": "skills/obsidian-markdown",
+      "commit": "a1dc48e68138490d522c04cbf5822214c6eb1202"
+    },
+    "react-doctor": {
+      "source": "github:millionco/react-doctor",
+      "path": "skills/react-doctor",
+      "commit": "a48fb06ffbe7221655e18529fcc954ecae17a22f"
+    },
+    "skill-creator": {
+      "source": "github:anthropics/skills",
+      "path": "skills/skill-creator",
+      "commit": "57546260929473d4e0d1c1bb75297be2fdfa1949",
+      "license": "Apache-2.0"
+    },
+    "supabase": {
+      "source": "github:supabase/agent-skills",
+      "path": "skills/supabase",
+      "version": "0.1.2",
+      "commit": "1356046015476711a769601079262b5635929427"
+    },
+    "supabase-postgres-best-practices": {
+      "source": "github:supabase/agent-skills",
+      "path": "skills/supabase-postgres-best-practices",
+      "commit": "1356046015476711a769601079262b5635929427",
+      "license": "MIT"
+    },
+    "tdd": {
+      "source": "github:mattpocock/skills",
+      "path": "skills/engineering/tdd",
+      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
+    },
+    "to-issues": {
+      "source": "github:mattpocock/skills",
+      "path": "skills/engineering/to-issues",
+      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
+    },
+    "to-prd": {
+      "source": "github:mattpocock/skills",
+      "path": "skills/engineering/to-prd",
+      "commit": "694fa30311e02c2639942308513555e61ee84a6f",
+      "modified": true
+    }
+  }
+}