/load-test | context-cascade

Library-First Directive

This agent operates under library-first constraints:

Pre-Check Required: Before writing code, search:
- .claude/library/catalog.json (components)
- .claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md (patterns)
- D:\Projects\* (existing implementations)
Decision Matrix:

Result Action
Library >90% REUSE directly
Library 70-90% ADAPT minimally
Pattern documented FOLLOW pattern
In existing project EXTRACT and adapt
No match BUILD new

Result	Action
Library >90%	REUSE directly
Library 70-90%	ADAPT minimally
Pattern documented	FOLLOW pattern
In existing project	EXTRACT and adapt
No match	BUILD new

Library-First Directive

This agent operates under library-first constraints:

Pre-Check Required: Before writing code, search:
- .claude/library/catalog.json (components)
- .claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md (patterns)
- D:\Projects\* (existing implementations)
Decision Matrix:

Result Action
Library >90% REUSE directly
Library 70-90% ADAPT minimally
Pattern documented FOLLOW pattern
In existing project EXTRACT and adapt
No match BUILD new

Result	Action
Library >90%	REUSE directly
Library 70-90%	ADAPT minimally
Pattern documented	FOLLOW pattern
In existing project	EXTRACT and adapt
No match	BUILD new

STANDARD OPERATING PROCEDURE

Purpose

Primary action: Primary input

Trigger Conditions

Command syntax: /load-test [args]
Ensure prerequisites are met before execution.

Inputs and Options

Inputs: No structured parameters defined; capture user intent explicitly.

Execution Phases

Review the request and confirm scope.
Execute the command flow.
Summarize outcomes and next actions.

Success Criteria and Outputs

Document artifacts, decisions, and follow-up actions clearly.

Error Handling and Recovery

If execution fails, capture the failure mode, retry with verbose context, and surface actionable remediation steps.

Chaining and Coordination

Memory and Tagging

Tag session outputs with who/when/why for traceability.

Example Invocation

/load-test example

Output Format

Provide a concise summary, actions taken, artifacts generated, and recommended next steps.
Always include an explicit confidence line: "Confidence: X.XX (ceiling: TYPE Y.YY)".
Use ceilings — inference/report: 0.70, research: 0.85, observation: 0.95, definition: 0.95.
Keep user-facing output in plain English; reserve VCL markers for the appendix only.

Confidence: 0.86 (ceiling: observation 0.95) - SOP rewritten to Prompt-Architect pattern based on legacy command content.

VCL COMPLIANCE APPENDIX (Internal Reference)

[[HON:teineigo]] [[MOR:root:PA]] [[COM:PromptArchitect]] [[CLS:ge_command]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:path:/commands]] [define|neutral] CONFIDENCE_CEILINGS := {inference:0.70, report:0.70, research:0.85, observation:0.95, definition:0.95} [conf:0.9] [state:confirmed] [direct|emphatic] L2_LANGUAGE := English; user-facing outputs exclude VCL markers. [conf:0.99] [state:confirmed] [commit|confident] <promise>LOAD_TEST_VERILINGUA_VERIX_COMPLIANT</promise> [conf:0.88] [state:confirmed]