メニュー
Governed workflow skill for transforming one frozen FEAT into a static HTML interactive prototype package with complete journey flow, UX button responses, and structured human review gating before UI spec derivation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
ADR-047 governed skill for initializing an API coverage manifest (api-coverage-manifest.yaml) from an api-test-plan, with capability × dimension expansion and four-dimensional status fields.
ADR-047 governed skill for generating structured API test specs from coverage items in api-coverage-manifest.yaml, with evidence_required, anti_false_pass_checks, and cleanup requirements.
ADR-047 governed skill for initializing an E2E coverage manifest (e2e-coverage-manifest.yaml) from an e2e-journey-plan, with four-dimensional status fields and journey-based coverage items.
ADR-047 governed skill for generating structured E2E journey specs from coverage items in e2e-coverage-manifest.yaml, with user steps, UI states, network events, anti_false_pass_checks, and evidence requirements.
ADR-047 governed skill for transforming one frozen FEAT into an API test plan (api-test-plan.md) with capability extraction, dimension matrix, and priority-based cut rules.
ADR-047 governed skill for deriving user journeys from a frozen prototype (or feat) and generating an E2E journey plan (e2e-journey-plan.md) with main journeys and minimum exception journeys.
| name | ll-dev-feat-to-proto |
| description | Governed workflow skill for transforming one frozen FEAT into a static HTML interactive prototype package with complete journey flow, UX button responses, and structured human review gating before UI spec derivation. |
This skill converts one selected frozen FEAT into one governed prototype_package.
The output is a static HTML prototype, not production frontend code.
When the selected FEAT belongs to a known journey (e.g. SRC001, SRC002) that requires a hi-fi template, the workflow emits a single journey-level prototype package (e.g. SRC001-JOURNEY) and reuses the same artifacts_dir across FEATs in that journey to avoid 001-005 producing duplicate prototypes.
E:\ai\LEE-Lite-skill-first\ssot\adr\ADR-041-FEAT-to-PROTOTYPE 前增加 Journey ASCII 产物并引入固定 UI Shell 引用基线.MD.ui_spec_package.ll.contract.yaml, input/contract.yaml, and output/contract.yaml.feat_freeze_package plus an explicit feat_ref.--input may be either the FEAT package directory or a formal.feat.* admission ref.python scripts/feat_to_proto.py run --input <feat-package-dir-or-formal-ref> --feat-ref <feat-ref> --repo-root <repo-root>.journey-ux-ascii.md as the Journey Structural Specui-shell-spec.md as a snapshot of the fixed UI Shell Sourceprototype/journey-model.json as the journey-level surface + main-path map used by downstream gates and reviewerssurface_map_package first and carry its surface_map_ref, prototype_owner_ref, prototype_action, ui_owner_ref, and ui_action into the emitted bundle.ui_shell_version, ui_shell_snapshot_hash, and shell_change_policy.python scripts/feat_to_proto.py freeze-guard --artifacts-dir <prototype-package-dir> succeeds.ll.contract.yamlinput/contract.yamloutput/contract.yamlagents/executor.mdagents/supervisor.mdscripts/validate_input.shscripts/validate_output.shscripts/freeze_guard.sh