ll-dev-feat-to-tech - SKILL.md Agent Skill

name: ll-dev-feat-to-tech description: Governed LL workflow skill for transforming one frozen FEAT inside a feat_freeze_package into a TECH-first design package with optional ARCH and API companions before downstream tech-impl work.

LL Dev FEAT to TECH

This skill is a lite-native governed workflow between ll-product-epic-to-feat and downstream tech-impl consumers. It turns one selected frozen FEAT into a design package where TECH is mandatory and ARCH / API are conditionally derived companions.

Canonical Authority

Workflow template: E:\ai\LEE\spec-global\departments\dev\workflows\templates\tech-design-l3-template.yaml
Upstream handoff: ll-product-epic-to-feat
Downstream workflow: workflow.dev.tech_to_impl
Primary runtime command: python scripts/feat_to_tech.py run --input <feat-package-dir> --feat-ref <feat-ref> --repo-root <repo-root>

Runtime Boundary Baseline

Classify this capability under E:\ai\LEE-Lite-skill-first\ssot\adr\ADR-038-运行时核心抽象边界与对象分层基线.MD.
This skill is a governed Skill and Workflow authority for FEAT -> TECH derivation. Its scripts and package files are carriers, not independent runtime authorities.

Required Read Order

ll.contract.yaml
input/contract.yaml
output/contract.yaml
resources/upstream-workflow-analysis.md
agents/executor.md
agents/supervisor.md
input/semantic-checklist.md and output/semantic-checklist.md

Execution Protocol

Accept only a freeze-ready feat_freeze_package emitted by ll-product-epic-to-feat, plus an explicit feat_ref, plus an explicit integration_context.
Validate the package structurally before drafting or editing any design output.
Resolve the authoritative FEAT context from feat-freeze-bundle.md, feat-freeze-bundle.json, inherited source_refs, the upstream acceptance evidence, and the frozen integration_context.
Run python scripts/feat_to_tech.py executor-run --input <feat-package-dir> --feat-ref <feat-ref> to generate the governed design package.
Always produce TECH; produce ARCH only when the FEAT is architecture-impacting; produce API only when a cross-boundary contract exists.
Record execution evidence, then hand the package to the supervisor.
Run python scripts/feat_to_tech.py supervisor-review --artifacts-dir <tech-package-dir> before freeze.
Freeze only after the supervisor records a semantic pass and python scripts/feat_to_tech.py freeze-guard --artifacts-dir <tech-package-dir> returns success.
Emit a downstream handoff that preserves feat_ref, tech_ref, optional arch_ref / api_ref, and the full integration and ownership refs needed by workflow.dev.tech_to_impl.
When external gate returns revise or retry, rerun run, executor-run, or supervisor-review with --revision-request <revision-request.json> so the regenerated design package preserves normalized revision context and evidence.

Workflow Boundary

Input: one feat_freeze_package plus one selected feat_ref plus integration_context
Output: one tech_design_package containing a mandatory TECH design object and optional ARCH / API design companions
Out of scope: direct implementation planning, TASK authoring, TESTSET authoring, or bypassing the governed FEAT to TECH boundary

Non-Negotiable Rules

Do not accept raw requirements, SRC candidates, EPIC packages, or standalone FEAT markdown outside a governed feat_freeze_package.
Do not treat ARCH and API as unconditional peers of TECH; they are conditional child artifacts decided by need assessment.
Do not let ARCH, TECH, and API restate the same material. ARCH owns system placement and boundaries, TECH owns implementation design, API owns external contracts.
Do not bypass the final cross-artifact consistency check before freeze.
Do not let the executor self-approve semantic validity.
Do not freeze unless integration_context_sufficient and stateful_design_present are explicitly recorded.
Do not let TECH omit internal state machine, key algorithm, input/output side effects, or canonical ownership facts that downstream implementation must inherit.