{"slug": "show-hn-executor-skill-superpowers-on-steroids", "title": "Show HN: Executor – Skill: Superpowers on Steroids", "summary": "Atri10 released Executor, an open-source initiative-scoped workflow system for coding agents that structures work from intake through review with a strict per-initiative ID namespace and separated thinking and execution stores. The system, available on GitHub, works with any agent that can read skill files from a directory and includes 10 skills covering phases from initiative intake to handoff, with evidence-backed completion and a safety scan before handoff.", "body_md": "An initiative-scoped workflow system for coding agents: it takes a major idea from intake through architecture, spec, plan, execution, and review, with a strict per-initiative ID namespace, separated thinking and execution stores, and evidence-backed completion.\n\nNothing floats. Every document, task, review, and ruling carries an ID that\nnames the initiative it belongs to. A body of work gets one **Initiative**;\nthe initiative owns a folder, an ID namespace, and every document produced\nabout it.\n\nWorks with any agent that can read skill files from a directory.\n\nClone the repo and copy the `skills/`\n\ndirectories into whatever directory\nyour agent loads skills from:\n\n```\ngit clone git@github.com:Atri10/executor.git\ncp -R executor/skills/* <your-agents-skills-dir>/\n```\n\nThen invoke the root router:\n\n```\n/skill:executor\n```\n\nor just say *\"start an initiative\"* — normal requests route by the skill's\nfrontmatter description.\n\n| Skill | Phase | Output |\n|---|---|---|\n`executor` |\nRouter + contract | Loads the right phase skill, defines the ID namespace |\n`executor-initiative` |\nIntake | Initiative folder, charter |\n`executor-discovery` |\nDiscovery | Research, options comparison |\n`executor-architecture` |\nArchitecture, Design | Architecture, ADRs, interfaces, component designs |\n`executor-spec` |\nSpecification | Spec, risks, verification strategy |\n`executor-planning` |\nPlanning | Plans with tasks |\n`executor-execution` |\nExecution | Commits, reports, ledger |\n`executor-review` |\nReview | Verdicts, findings, rulings |\n`executor-verification` |\nVerification | Evidence of working software |\n`executor-handoff` |\nHandoff | Merged branch, updated indexes |\n\n**Phases compress, they never vanish.** A small initiative can produce a\ncharter and a spec in one exchange and skip discovery — but skipping is a\nstated decision recorded in the charter, not an omission.\n\n```\nflowchart LR\n    subgraph THINK[\"docs/executor/ - tracked\"]\n        C[\"Charter\"] --> R[\"Research, Options\"]\n        R --> A[\"Architecture, ADRs, Interfaces\"]\n        A --> D[\"Design\"]\n        D --> S[\"Spec\"]\n        S --> P[\"Plans\"]\n    end\n    subgraph EXEC[\".executor/ - git-ignored by default\"]\n        L[\"Ledger, Rulings\"]\n        B[\"Briefs\"]\n        RP[\"Reports\"]\n        V[\"Diffs, Verdicts\"]\n    end\n    P -->|\"each task dispatch\"| B\n    B --> RP\n    RP --> V\n    V --> L\n```\n\n— the thinking record. Git-tracked: charter, research, architecture, decisions, interfaces, design, spec, risks, plans. A reader who clones the repo gets the complete reasoning.`docs/executor/`\n\n— the execution record. Git-ignored by default, safe to commit if you choose: task briefs, implementer reports, review diffs and verdicts, the progress ledger, rulings. Never deleted — the reasoning is the point.`.executor/`\n\nThe split is durability-of-audience, not durability-of-value.\n\n```\nINIT-0004                      the initiative\nINIT-0004-CHTR-01              its charter\nINIT-0004-RSCH-02              a research note\nINIT-0004-SPEC-01-R07          requirement 7 inside that spec\nINIT-0004-P01                  a plan\nINIT-0004-P01-T03              task 3 of that plan\nINIT-0004-P01-T03-R02          review round 2 of that task\n```\n\nAddressable requirements are what let a review finding name the exact contract it violates, and what lets a plan task declare precisely which requirements it discharges.\n\n`.executor/`\n\nmay be committed, so everything in both stores is written as\nthough it will be public. Credentials, tokens, and personal data never go\ninto any Executor artifact — a redacted existence statement and a safe path\ninstead. `skills/executor/references/safety.md`\n\ndefines the required scan\nbefore any handoff.\n\n| Doc | Purpose |\n|---|---|\n|", "url": "https://wpnews.pro/news/show-hn-executor-skill-superpowers-on-steroids", "canonical_source": "https://github.com/Atri10/executor", "published_at": "2026-09-01 17:12:01+00:00", "updated_at": "2026-09-01 17:22:49.047829+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents"], "entities": ["Atri10", "Executor", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/show-hn-executor-skill-superpowers-on-steroids", "markdown": "https://wpnews.pro/news/show-hn-executor-skill-superpowers-on-steroids.md", "text": "https://wpnews.pro/news/show-hn-executor-skill-superpowers-on-steroids.txt", "jsonld": "https://wpnews.pro/news/show-hn-executor-skill-superpowers-on-steroids.jsonld"}}