outcomeengineering
- 56 skills
- 0 followers
- 1 day ago last updated
- ▌ Testing 2 · outcomeengineering bundleALWAYS invoke this skill before writing tests or when learning the testing approach.
- ▌ Committing Changes 2 · outcomeengineering bundleALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.
- ▌ Testing · outcomeengineeringALWAYS invoke this skill before writing tests or when learning the testing approach.
- ▌ Reviewing Vhdl · outcomeengineering bundleALWAYS invoke this skill when reviewing VHDL code for idiomatic style, synthesizability, or best practices. NEVER review VHDL without this skill.
- ▌ Aligning · outcomeengineeringALWAYS invoke this skill when reviewing, auditing, or checking spec file conformance. NEVER check spec conformance without this skill.
- ▌ Applying · outcomeengineering bundleALWAYS invoke this skill before implementing any spec-tree work item. NEVER write code for a spec-tree node without this skill.
- ▌ Writing Prose · outcomeengineeringALWAYS invoke this skill when generating articles, documentation, blog posts, specs, or any long-form text. NEVER write long-form text without this skill.
- ▌ Authoring · outcomeengineeringALWAYS invoke this skill when adding, defining, or creating specs, decisions, or nodes. NEVER author spec tree artifacts without this skill.
- ▌ Coding Python · outcomeengineeringALWAYS invoke this skill when writing or fixing implementation code for Python.
- ▌ Managing Specs · outcomeengineering bundleALWAYS invoke this skill when creating or organizing specs, capabilities, features, stories, or ADRs. NEVER create, read, or modify any files in the specs/ directory without this skill.
- ▌ Excalidrawing · outcomeengineering bundleALWAYS invoke this skill when creating Excalidraw diagrams, visualizing workflows, architectures, or concepts. NEVER generate Excalidraw JSON without this skill.
- ▌ Reviewing Prose · outcomeengineeringALWAYS invoke this skill when reviewing, editing, or improving prose for quality. NEVER review prose without this skill.
- ▌ Testing Python · outcomeengineeringALWAYS invoke this skill when writing or fixing tests for Python.
- ▌ Decomposing · outcomeengineeringALWAYS invoke this skill when breaking down, splitting, scoping, or structuring spec tree nodes. NEVER decompose specs without this skill.
- ▌ Refactoring · outcomeengineeringALWAYS invoke this skill when moving nodes, re-scoping content, or extracting shared enablers. NEVER restructure the spec tree without this skill.
- ▌ Auditing Skills · outcomeengineeringALWAYS invoke this skill when auditing, reviewing, or evaluating SKILL.md files. NEVER audit skills without this skill.
- ▌ Creating Skills · outcomeengineering bundleALWAYS invoke this skill when creating, editing, or improving SKILL.md files. NEVER create or modify skills without this skill.
- ▌ Reviewing Tests · outcomeengineeringFoundational test review methodology. Loaded by /auditing-python-tests and /auditing-typescript-tests, not invoked directly.
- ▌ Auditing Python · outcomeengineering bundleALWAYS invoke this skill when auditing code for Python or after writing code. NEVER modify a spec to match code without auditing the code first.
- ▌ Writing Prd · outcomeengineering bundleALWAYS invoke this skill when writing PRDs or product requirements. NEVER write PRDs without this skill.
- ▌ Bootstrapping · outcomeengineering bundleALWAYS invoke this skill when setting up a new spec tree or when /authoring detects an empty spx/ directory. NEVER create a spec tree from scratch without this skill.
- ▌ Understanding · outcomeengineering bundleALWAYS invoke this skill before any spec-tree work to load methodology. NEVER create, read, or modify spec tree files without loading this foundation first.
- ▌ Managing Spx · outcomeengineering bundleALWAYS invoke this skill when creating or organizing specs, capabilities, features, stories, or ADRs. NEVER create, read, or modify any files in the spx/ directory without this skill.
- ▌ Auditing Commands · outcomeengineeringALWAYS invoke this skill when auditing, reviewing, or evaluating slash command .md files. NEVER audit slash commands without this skill.
- ▌ Creating Commands · outcomeengineering bundleALWAYS invoke this skill when creating or editing slash commands. NEVER create slash commands without this skill.
- ▌ Auditing Tests · outcomeengineering bundleALWAYS invoke this skill when auditing test evidence quality, after writing tests for a spec node, or before closing an outcome.
- ▌ Auditing Subagents · outcomeengineeringALWAYS invoke this skill when auditing, reviewing, or evaluating subagent configuration files. NEVER audit subagents without this skill.
- ▌ Creating Subagents · outcomeengineering bundleALWAYS invoke this skill when creating, editing, or configuring subagents. NEVER create subagents without this skill.
- ▌ Committing Changes · outcomeengineeringALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.
- ▌ Standardizing Prose · outcomeengineeringProse anti-patterns enforced across all skills. Loaded by other skills, not invoked directly.
- ▌ Contextualizing · outcomeengineeringALWAYS invoke this skill when asking about status, progress, or what exists in the spec tree. NEVER work on any part of the spec tree without loading context through this skill first.
- ▌ Understanding Specs · outcomeengineering bundleALWAYS invoke this skill before implementing any work item to load complete context. NEVER create, read, or modify any files in the specs/ directory without this skill.
- ▌ Architecting Python · outcomeengineering bundleALWAYS invoke this skill when writing ADRs for Python.
- ▌ Designing Frontend · outcomeengineeringALWAYS invoke this skill when designing or building web components, pages, or dashboards. NEVER design or build web UI without this skill.
- ▌ Reviewing Systemverilog · outcomeengineering bundleALWAYS invoke this skill when reviewing SystemVerilog or Verilog code for idiomatic style, synthesizability, or best practices. NEVER review SystemVerilog or Verilog without this skill.
- ▌ Standardizing Python · outcomeengineeringPython code standards enforced across all skills. Loaded by other skills, not invoked directly.
- ▌ Auditing Python Tests · outcomeengineeringALWAYS invoke this skill when auditing tests for Python or after writing tests. NEVER use auditing-python for test code.
- ▌ Understanding Spx · outcomeengineering bundleALWAYS invoke this skill before implementing any work item to load complete context. NEVER create, read, or modify any files in the spx/ directory without this skill.
- ▌ Coding Typescript · outcomeengineering bundleALWAYS invoke this skill when writing or fixing implementation code for TypeScript.
- ▌ Testing Typescript · outcomeengineering bundleALWAYS invoke this skill when writing or fixing tests for TypeScript.
- ▌ Auditing Typescript · outcomeengineering bundleALWAYS invoke this skill when auditing code for TypeScript or after writing code. NEVER modify a spec to match code without auditing the code first.
- ▌ Migrating Spec To Spx · outcomeengineeringALWAYS invoke this skill when migrating specs to spx, reviewing migrations, or debugging migration issues. NEVER migrate specs without this skill.
- ▌ Architecting Typescript · outcomeengineering bundleALWAYS invoke this skill when writing ADRs for TypeScript.
- ▌ Auditing Python Architecture · outcomeengineering bundleALWAYS invoke this skill when auditing ADRs for Python or after writing an ADR. NEVER implement from an unaudited ADR.
- ▌ Standardizing Python Testing · outcomeengineeringPython testing standards enforced across all skills. Loaded by other skills, not invoked directly.
- ▌ Standardizing Typescript · outcomeengineeringTypeScript code standards enforced across all skills. Loaded by other skills, not invoked directly.
- ▌ Auditing Product Decisions · outcomeengineering bundleALWAYS invoke this skill when auditing PDRs or after writing a PDR. NEVER audit PDRs without this skill.
- ▌ Understanding Durable Map · outcomeengineeringALWAYS invoke this skill when agents think in tasks or backlogs, want to "close" items, or ask where "done" work goes. NEVER treat specs as work items without this skill.
- ▌ Auditing Typescript Tests · outcomeengineeringALWAYS invoke this skill when auditing tests for TypeScript or after writing tests. NEVER use auditing-typescript for test code.
- ▌ Standardizing Python Architecture · outcomeengineeringPython ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.
- ▌ Decomposing Feature To Stories · outcomeengineeringALWAYS invoke this skill when breaking down a feature into stories. NEVER decompose features without this skill.
- ▌ Decomposing Prd To Capabilities · outcomeengineeringALWAYS invoke this skill when breaking down a PRD into capabilities. NEVER decompose PRDs without this skill.
- ▌ Auditing Typescript Architecture · outcomeengineering bundleALWAYS invoke this skill when auditing ADRs for TypeScript or after writing an ADR. NEVER implement from an unaudited ADR.
- ▌ Decomposing Capability To Features · outcomeengineeringALWAYS invoke this skill when breaking down a capability into features. NEVER decompose capabilities without this skill.
- ▌ Understanding Outcome Decomposition · outcomeengineering bundleALWAYS invoke this skill before using any decomposition skill or when understanding outcome levels. NEVER decompose outcomes without loading this foundation first.
- ▌ Standardizing Typescript Architecture · outcomeengineeringTypeScript ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.