← gstack WorkflowsCONTENT HISTORY

Update to gstack Workflows

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Produce a retrospective from repository evidence, delivery outcomes, and recorded learnings.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 273
    }
  ],
  "name": "retro",
  "skill_md_contents": "---\nname: retro\ndescription: Produce a retrospective from repository evidence, delivery outcomes, and recorded learnings.\n---\n\n# Retro\n\nPortable ChatGPT/Codex adaptation of the `retro` workflow from `garrytan/gstack`. Preserve the original job and safety intent while mapping execution to capabilities the current host actually exposes.\n\n## When to use\n\nUse this Skill when the user explicitly names `retro` or asks for the same job described above.\n\n## Host contract\n\n- Inspect repository or file evidence before making claims about the current state.\n- Use host-native read, list, search, grep, patch, write, shell, browser, computer, and Python capabilities only when they actually exist.\n- Never claim commands, tests, browser actions, device actions, file writes, Git operations, or external mutations that were not executed.\n- Prefer read-only discovery before mutation.\n- Respect repository instructions and preserve unrelated work.\n- When the original native gstack runtime is available in Codex, it may be used as an implementation detail after inspecting the installed upstream Skill. Do not hard-code Claude-only paths as a requirement.\n\n## Workflow\n\n1. Gather the evidence relevant to the period or work being analyzed.\n2. Separate observed outcomes from interpretation.\n3. Identify recurring friction, successful patterns, and unresolved issues.\n4. Produce specific follow-up actions tied to evidence.\n5. Do not invent activity metrics that are not present in the source data.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}

SHA-256 of public snapshot: e3d19ff8c9f7e292592988fe60b2443f1fe17c27128b7dffe89a30b82ce53380