This directory is the mock sample. It demonstrates the Template Method idea with an RFP workflow; it is not the Superpowers implementation.

flowchart LR
    R[Root template Skill] --> A[Extract]
    A --> B[Analyze gaps]
    B --> H[Domain hook]
    H --> D[Draft]
    D --> Q[Quality check]
    H -.-> S[Healthcare / Finance child Skill]

The pattern-bearing line is: fixed root sequence → one overridable hook → fixed remaining sequence.

sample/
├── SKILL.md
├── child-skills/{healthcare,finance}/SKILL.md
├── references/rfp-domain-hook-contract.md
├── scripts/run_demo.py
└── tests/test_demo.py

<!-- Template Method: only the domain hook is supplied by a child Skill. -->
extract -> analyze-gaps -> apply-domain-hook -> draft -> quality-check
                         ^
                         └── healthcare or finance child Skill

1. Write the invariant sequence in the root Skill.
2. Define each hook's exact input and output.
3. Let child Skills provide hook content only.
4. Test that children cannot skip, add, or reorder root stages.

Every enterprise RFP response must extract requirements, analyze gaps, apply a domain hook, draft the response, and quality-check it in that order. Healthcare and finance need different domain evidence without changing the mandatory workflow.

The root Skill owns the invariant five-stage template. Healthcare and Finance child Skills implement only the bounded apply-domain-hook operation; they cannot reorder, skip, or replace the template.

Input: RFP identity, domain, requirements, and source material. Output: the same ordered stage trace, domain hook result, draft, and quality result. Hook failure stops the template before drafting and quality checking.

• Root Skill defines the invariant sequence and hook boundary.
• Hook contract defines the only specialization point.
• scripts/run_demo.py and the healthcare/finance fixtures show substitution without reordering.

Run from this directory with Python 3.10 or newer:

python3 scripts/run_demo.py
python3 scripts/run_demo.py fixtures/valid/finance-rfp.json
python3 -m unittest discover tests -v

The default result is byte-for-byte equal to expected/healthcare-rfp-result.json. Invalid fixtures produce the matching stable error files with exit status 2. The demo uses only the Python standard library and performs no network or cross-pattern imports.

The tests prove the literal run_rfp("healthcare") API, fixed order, exactly one hook invocation, failure stop, shared hook contract, bounded substitution, explicit AbstractClass dispatch, inherited mixin run irrelevance, direct override admission, static hook signature validation, ordinary hook-argument copy mutation, unknown stage-claim rejection, deterministic outputs, duplicate-member rejection, Unicode handling, and depth/type bounds. Focused tests and the oracle use only the Python standard library.

Hooks are cooperative, trusted extension code. The sample does not claim sandboxing or protection from closures, module globals, monkeypatching, introspection, or other arbitrary in-process Python behavior.

Domain findings are illustrative, not professional RFP or compliance advice.