ship-tasks

{
  "name": "ship-tasks",
  "version": "0.1.7+codex.20260826131957",
  "description": "Compose backlog scope and deliver selected Task Manager work with autonomous test fixtures, strategic explanations, and explicit critical-codebase acceptance.",
  "author": {
    "name": "Andrey Myasnikov",
    "url": "https://github.com/xxsrez"
  },
  "homepage": "https://github.com/xxsrez/ShipTask",
  "repository": "https://github.com/xxsrez/marketplace",
  "keywords": [
    "tasks",
    "planning",
    "decomposition",
    "delivery",
    "verification",
    "releases",
    "communication",
    "explanation",
    "productivity"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "Ship Tasks",
    "shortDescription": "Compose backlog scope and deliver verified work.",
    "longDescription": "Includes three sibling skills. Task Composer formulates drafts and, on explicit planning intent, creates one Backlog Task or a problem-first Epic with concrete subtasks, existing Labels, native hierarchy, and semantic relations. It keeps classification in Labels and hierarchy instead of duplicating Bug, Epic, or similar type prefixes in titles. It never implements the work, never guesses an unknown current Release, and does not expand Label taxonomy. Ship Tasks delivers selected Task Manager scope to verified outcomes with truthful lifecycle state, readable native comments, visible acceptance incidents, autonomous synthetic test fixtures, and authority boundaries. Each Task gets a lightweight targeted gate; compatible candidates are periodically reviewed and released to UAT as one exact integrated batch, without deploying every Task or asking an extra approval for ordinary non-production UAT. If fresh scope has no To Do or In Progress work and every remaining In Review Task is genuinely blocked on substantial human verification, one fresh read-only critic may ground a weaker critical-codebase acceptance from code, tests, and exact project context. Every such transition is explicitly commented with the missing functional check, blocker reason, critic verdict, and residual risk; defects return to In Progress, while stale or inconclusive reviews remain In Review. It must create standard test inputs itself when safe, and when a genuine external blocker remains it publishes a causal blocker report with recommended test paths, prerequisites, success signals, and exact resume conditions. Before a terminal blocker claim, Ship Tasks reads a fresh Strategic Explainer result as reflection input, verifies any newly visible safe path against primary evidence, and continues instead of publishing a stale blocker when that path works. Project, Release, and current-scope selectors stay live: matching non-Backlog Tasks enter delivery without repeated approval. A blocked-by relation opens dependent implementation after the required upstream contract is merged into the exact integration candidate; upstream Done is not required, pending acceptance remains visible, and later defects invalidate only attributed downstream results. Browser or controller changes remain diagnostic paths rather than repairs or substitutes for proven product failures. It preserves natural-language subagent rules for counts, roles, opt-outs, and conditions; otherwise it chooses useful independent delegation automatically and isolates concurrent implementation writers in separate feature branches and Git worktrees. Across interruptions or sessions it resumes unfinished task-owned Git work when prior ownership is safely inactive and exclusive. Only genuinely simple predictable packets use Luna Max, and Luna uncertainty returns to the current model profile. When host title capability, first-turn identity, and a catalog placeholder are proven, it makes at most one best-effort scope-based title attempt without overwriting meaningful titles; missing, deferred, or failed capability never blocks delivery. A delivery verb alone does not activate Ship Tasks. Strategic Explainer is an isolated read-only provider behind an opaque router: each user-facing publication unit gets a new default subagent with fork isolation, one short task, exact scope, and resolvable source anchors without caller analysis or candidate text. The caller never receives or applies the provider method, accepts ready text and source basis or a refusal, and uses a new clean subagent for corrections. Provider unavailability does not enable caller-side imitation, and the provider never takes status, scope, authority, or execution decisions.",
    "developerName": "Andrey Myasnikov",
    "category": "Productivity",
    "capabilities": [
      "Interactive",
      "Write"
    ],
    "websiteURL": "https://task-manager.xxsrez-work.chatgpt.site",
    "defaultPrompt": [
      "Use Task Composer to turn this requirement into one Backlog Task or a strategic Epic with concrete subtasks",
      "Deliver TM-123 to a verified terminal outcome",
      "Create exactly one Task in Task Manager and immediately start delivering it"
    ],
    "brandColor": "#6D5CE7"
  }
}