菜单
Use to design the technical approach for a spec — the strategy, components, data flow, dependencies, and integration points, with the steps and gates that make it buildable. Produces the implementation plan, from the PLAN template, consistent with the project's existing architecture.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Keep commits atomic — split a mixed change set into scoped, reviewable commits.
The one-time procedure to take an exported project to live — understand it, confirm the name/goal/stack with the user, run the deterministic `aspis bootstrap`, enrich the judgment files (AGENTS.md, ARCHITECTURE, context), verify, and let the package self-clean. Followed by the bootstrap agent.
Keep per-subsystem architectural intent current through the planning loop — read before designing, record an impact report on change, confirm with the user, apply a dated update, and verify the build against approved intent.
Audit a plan's task dependency graph for structural integrity — circular dependencies, missing prerequisites, orphan tasks, and dependency classification (hard/soft/warning). Produces a pass/warn/fail audit report per dependency so planners catch graph errors before build starts.
Every editing agent should start on a clean working tree so parallel work never collides.
Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.
| name | architecture-planning |
| description | Use to design the technical approach for a spec — the strategy, components, data flow, dependencies, and integration points, with the steps and gates that make it buildable. Produces the implementation plan, from the PLAN template, consistent with the project's existing architecture. |
Turn what (the spec) into how — a technical approach that fits the existing system, names its risks, and is concrete enough to decompose into tasks.
After the spec is settled, for any work that touches code or system structure.
Fill the .aspis/templates/planning/PLAN.md template. Keep architecture decisions that need
human approval flagged, not silently made.
