Automate Spec Tree artifact authoring from intake to validated creation.
npx skills add https://github.com/outcomeeng/claude --skill authoring
Please help me install this Agent Skill. Skill: authoring Source: https://github.com/outcomeeng/claude/tree/main/plugins/spec-tree/skills/authoring Command: npx skills add https://github.com/outcomeeng/claude --skill authoring
The Skill ensures consistent and correct authoring of Spec Tree artifacts by providing a structured workflow that guides users from intake to artifact creation, enforcing templates, placement, and quality rules so artifacts are immediately usable by agents.
Check for the SPEC_TREE_FOUNDATION marker and invoke the understanding skill if missing, then draft artifacts using the templates from the understanding skill.
High-intent search queries and answers about installing and using this skill.
A Spec Tree is a structured hierarchy of product specs, ADRs, PDRs, and outcome nodes. You need structured authoring to ensure consistent placement, template usage, and compliance so artifacts remain immediately usable by agents.
To draft an architecture decision record or product spec, the workflow guides you from intake through artifact creation, loading templates from the understanding skill and enforcing atemporal voice and test-link rules before validating the draft.
Yes, artifact authoring requires templates from the understanding skill and the SPEC_TREE_FOUNDATION marker. If the marker is missing, you must invoke the understanding skill to establish the foundation before drafting.
The authoring workflow validates drafts against a strict checklist that enforces atemporal voice and test-link rules, ensuring compliance and tree integrity before artifacts are created in the correct spx paths.
The best way to maintain tree integrity is through automated placement and context rules applied during intake, which ensure enabler nodes and outcome nodes are correctly structured within the parent spec-tree hierarchy.
The workflow supports product specs, ADRs, PDRs, enabler nodes, and outcome nodes. Artifacts outside these types or drafts failing the strict compliance checklist cannot be created through this automated process.
outcomeengLoad Spec Tree core references and emit a <SPEC_TREE_FOUNDATION> marker.
tae2089Route design briefs to production specs within agent-team workflows.
connor-git-yamlExecute the Spec Driver workflow in Codex while preserving artifact gates and outputs.
csackriderOrganizes feature specs and ADRs using standardized templates and naming conventions.
