all publishers

outcomeengineering

@outcomeengineering source repo

56 published skills

  1. ▌
    Testing 2 · outcomeengineering bundle
    ALWAYS invoke this skill before writing tests or when learning the testing approach.
    1 repo stars
  2. ▌
    Committing Changes 2 · outcomeengineering bundle
    ALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.
    1 repo stars
  3. ▌
    Testing · outcomeengineering
    ALWAYS invoke this skill before writing tests or when learning the testing approach.
    1 repo stars
  4. ▌
    Reviewing Vhdl · outcomeengineering bundle
    ALWAYS invoke this skill when reviewing VHDL code for idiomatic style, synthesizability, or best practices. NEVER review VHDL without this skill.
    1 repo stars
  5. ▌
    Aligning · outcomeengineering
    ALWAYS invoke this skill when reviewing, auditing, or checking spec file conformance. NEVER check spec conformance without this skill.
    1 repo stars
  6. ▌
    Applying · outcomeengineering bundle
    ALWAYS invoke this skill before implementing any spec-tree work item. NEVER write code for a spec-tree node without this skill.
    1 repo stars
  7. ▌
    Writing Prose · outcomeengineering
    ALWAYS invoke this skill when generating articles, documentation, blog posts, specs, or any long-form text. NEVER write long-form text without this skill.
    1 repo stars
  8. ▌
    Authoring · outcomeengineering
    ALWAYS invoke this skill when adding, defining, or creating specs, decisions, or nodes. NEVER author spec tree artifacts without this skill.
    1 repo stars
  9. ▌
    Coding Python · outcomeengineering
    ALWAYS invoke this skill when writing or fixing implementation code for Python.
    1 repo stars
  10. ▌
    Managing Specs · outcomeengineering bundle
    ALWAYS 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.
    1 repo stars
  11. ▌
    Excalidrawing · outcomeengineering bundle
    ALWAYS invoke this skill when creating Excalidraw diagrams, visualizing workflows, architectures, or concepts. NEVER generate Excalidraw JSON without this skill.
    1 repo stars
  12. ▌
    Reviewing Prose · outcomeengineering
    ALWAYS invoke this skill when reviewing, editing, or improving prose for quality. NEVER review prose without this skill.
    1 repo stars
  13. ▌
    Testing Python · outcomeengineering
    ALWAYS invoke this skill when writing or fixing tests for Python.
    1 repo stars
  14. ▌
    Decomposing · outcomeengineering
    ALWAYS invoke this skill when breaking down, splitting, scoping, or structuring spec tree nodes. NEVER decompose specs without this skill.
    1 repo stars
  15. ▌
    Refactoring · outcomeengineering
    ALWAYS invoke this skill when moving nodes, re-scoping content, or extracting shared enablers. NEVER restructure the spec tree without this skill.
    1 repo stars
  16. ▌
    Auditing Skills · outcomeengineering
    ALWAYS invoke this skill when auditing, reviewing, or evaluating SKILL.md files. NEVER audit skills without this skill.
    1 repo stars
  17. ▌
    Creating Skills · outcomeengineering bundle
    ALWAYS invoke this skill when creating, editing, or improving SKILL.md files. NEVER create or modify skills without this skill.
    1 repo stars
  18. ▌
    Reviewing Tests · outcomeengineering
    Foundational test review methodology. Loaded by /auditing-python-tests and /auditing-typescript-tests, not invoked directly.
    1 repo stars
  19. ▌
    Auditing Python · outcomeengineering bundle
    ALWAYS invoke this skill when auditing code for Python or after writing code. NEVER modify a spec to match code without auditing the code first.
    1 repo stars
  20. ▌
    Writing Prd · outcomeengineering bundle
    ALWAYS invoke this skill when writing PRDs or product requirements. NEVER write PRDs without this skill.
    1 repo stars
  21. ▌
    Bootstrapping · outcomeengineering bundle
    ALWAYS 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.
    1 repo stars
  22. ▌
    Understanding · outcomeengineering bundle
    ALWAYS invoke this skill before any spec-tree work to load methodology. NEVER create, read, or modify spec tree files without loading this foundation first.
    1 repo stars
  23. ▌
    Managing Spx · outcomeengineering bundle
    ALWAYS 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.
    1 repo stars
  24. ▌
    Auditing Commands · outcomeengineering
    ALWAYS invoke this skill when auditing, reviewing, or evaluating slash command .md files. NEVER audit slash commands without this skill.
    1 repo stars
  25. ▌
    Creating Commands · outcomeengineering bundle
    ALWAYS invoke this skill when creating or editing slash commands. NEVER create slash commands without this skill.
    1 repo stars
  26. ▌
    Auditing Tests · outcomeengineering bundle
    ALWAYS invoke this skill when auditing test evidence quality, after writing tests for a spec node, or before closing an outcome.
    1 repo stars
  27. ▌
    Auditing Subagents · outcomeengineering
    ALWAYS invoke this skill when auditing, reviewing, or evaluating subagent configuration files. NEVER audit subagents without this skill.
    1 repo stars
  28. ▌
    Creating Subagents · outcomeengineering bundle
    ALWAYS invoke this skill when creating, editing, or configuring subagents. NEVER create subagents without this skill.
    1 repo stars
  29. ▌
    Committing Changes · outcomeengineering
    ALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.
    1 repo stars
  30. ▌
    Standardizing Prose · outcomeengineering
    Prose anti-patterns enforced across all skills. Loaded by other skills, not invoked directly.
    1 repo stars
  31. ▌
    Contextualizing · outcomeengineering
    ALWAYS 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.
    1 repo stars
  32. ▌
    Understanding Specs · outcomeengineering bundle
    ALWAYS 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.
    1 repo stars
  33. ▌
    Architecting Python · outcomeengineering bundle
    ALWAYS invoke this skill when writing ADRs for Python.
    1 repo stars
  34. ▌
    Designing Frontend · outcomeengineering
    ALWAYS invoke this skill when designing or building web components, pages, or dashboards. NEVER design or build web UI without this skill.
    1 repo stars
  35. ▌
    Reviewing Systemverilog · outcomeengineering bundle
    ALWAYS invoke this skill when reviewing SystemVerilog or Verilog code for idiomatic style, synthesizability, or best practices. NEVER review SystemVerilog or Verilog without this skill.
    1 repo stars
  36. ▌
    Standardizing Python · outcomeengineering
    Python code standards enforced across all skills. Loaded by other skills, not invoked directly.
    1 repo stars
  37. ▌
    Auditing Python Tests · outcomeengineering
    ALWAYS invoke this skill when auditing tests for Python or after writing tests. NEVER use auditing-python for test code.
    1 repo stars
  38. ▌
    Understanding Spx · outcomeengineering bundle
    ALWAYS 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.
    1 repo stars
  39. ▌
    Coding Typescript · outcomeengineering bundle
    ALWAYS invoke this skill when writing or fixing implementation code for TypeScript.
    1 repo stars
  40. ▌
    Testing Typescript · outcomeengineering bundle
    ALWAYS invoke this skill when writing or fixing tests for TypeScript.
    1 repo stars
  41. ▌
    Auditing Typescript · outcomeengineering bundle
    ALWAYS invoke this skill when auditing code for TypeScript or after writing code. NEVER modify a spec to match code without auditing the code first.
    1 repo stars
  42. ▌
    Migrating Spec To Spx · outcomeengineering
    ALWAYS invoke this skill when migrating specs to spx, reviewing migrations, or debugging migration issues. NEVER migrate specs without this skill.
    1 repo stars
  43. ▌
    Architecting Typescript · outcomeengineering bundle
    ALWAYS invoke this skill when writing ADRs for TypeScript.
    1 repo stars
  44. ▌
    Auditing Python Architecture · outcomeengineering bundle
    ALWAYS invoke this skill when auditing ADRs for Python or after writing an ADR. NEVER implement from an unaudited ADR.
    1 repo stars
  45. ▌
    Standardizing Python Testing · outcomeengineering
    Python testing standards enforced across all skills. Loaded by other skills, not invoked directly.
    1 repo stars
  46. ▌
    Standardizing Typescript · outcomeengineering
    TypeScript code standards enforced across all skills. Loaded by other skills, not invoked directly.
    1 repo stars
  47. ▌
    Auditing Product Decisions · outcomeengineering bundle
    ALWAYS invoke this skill when auditing PDRs or after writing a PDR. NEVER audit PDRs without this skill.
    1 repo stars
  48. ▌
    Understanding Durable Map · outcomeengineering
    ALWAYS 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.
    1 repo stars
  49. ▌
    Auditing Typescript Tests · outcomeengineering
    ALWAYS invoke this skill when auditing tests for TypeScript or after writing tests. NEVER use auditing-typescript for test code.
    1 repo stars
  50. ▌
    Standardizing Python Architecture · outcomeengineering
    Python ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.
    1 repo stars
  51. ▌
    Decomposing Feature To Stories · outcomeengineering
    ALWAYS invoke this skill when breaking down a feature into stories. NEVER decompose features without this skill.
    1 repo stars
  52. ▌
    Decomposing Prd To Capabilities · outcomeengineering
    ALWAYS invoke this skill when breaking down a PRD into capabilities. NEVER decompose PRDs without this skill.
    1 repo stars
  53. ▌
    Auditing Typescript Architecture · outcomeengineering bundle
    ALWAYS invoke this skill when auditing ADRs for TypeScript or after writing an ADR. NEVER implement from an unaudited ADR.
    1 repo stars
  54. ▌
    Decomposing Capability To Features · outcomeengineering
    ALWAYS invoke this skill when breaking down a capability into features. NEVER decompose capabilities without this skill.
    1 repo stars
  55. ▌
    Understanding Outcome Decomposition · outcomeengineering bundle
    ALWAYS invoke this skill before using any decomposition skill or when understanding outcome levels. NEVER decompose outcomes without loading this foundation first.
    1 repo stars
  56. ▌
    Standardizing Typescript Architecture · outcomeengineering
    TypeScript ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.
    1 repo stars