Aek Design Feature

---
name: aek-design-feature
description: Use when designing a new capability or material architecture or public-contract change in a project with adopted AEK rules. Excludes wording-only changes, settled small fixes, review-only requests and implementation of an approved design.
---

# Design a project feature

Produce a technical design grounded in the affected project's owners and selected
engineering standards. Use the [project-skill contract](../../../standards/project-skills.md)
for local input resolution, procedure composition and the design result.

1. Reuse the requested outcome, existing design decisions and canonical task.
   Read the affected project entry/passport and enough implementation to identify
   current owners, contracts, versions and accepted exceptions. Resolve only
   missing facts that affect the design.
2. Select the local profile entries for the actual stack, then their relevant
   topic sections. Connect those rules to the changed boundary, state/resource
   owner or dependency decision; avoid a generic architecture checklist.
3. Use the applicable Superpowers procedure through the local adaptations if it
   is available and still needed. Keep one design/planning process and task store.
4. Record the chosen owners and paths, interface/compatibility decisions,
   consequential alternatives, open questions and observable acceptance checks
   in that task's permitted design location. Separate current facts, proposed
   changes and checks that have actually run.

A settled small fix returns to the implementation task without starting a design
phase. Missing guidance is reported with its affected decision under the local
contract; it does not trigger adoption, model setup, delegation or an installation.