Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

config-management

Étoiles2

Forks0

Mis à jour23 juin 2026 à 06:14

How the System Lead safely changes project configuration — model routing, build mode, policy config, and stack — only through the aspis commands and the config data files, never by hand-editing a rendered runtime agent. Reachable user → project-lead → system-lead, or user → system-lead directly.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

mahmoud-emad-dev

mahmoud-emad-dev/aspis

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Autres occupations informatiquesProfessions informatiques et mathématiques·SOC 15-1299

SKILL.md

readonly

name	config-management
description	How the System Lead safely changes project configuration — model routing, build mode, policy config, and stack — only through the aspis commands and the config data files, never by hand-editing a rendered runtime agent. Reachable user → project-lead → system-lead, or user → system-lead directly.

Config management

The System Lead owns every change to how the project is configured. Change configuration only through the aspis commands and the data files below — never hand-edit a rendered runtime agent (.opencode/ / .claude/); the adapters regenerate those from the catalog + config. Model routing and permission changes are human-gated (R-008): confirm with the user before applying.

Model routing (which model each agent uses)

See what's available: aspis models --available — the valid provider/model ids for this machine.
Edit the data, not the agents:
- one tier for everyone → .aspis/config/models.yaml (the tier → model map);
- one agent → .aspis/config/agent-models.yaml (per-agent pin; aspis models --sync (re)generates it).
Make it live: aspis models --sync --apply — refresh the editable file, then re-render the agents.

Build mode (rigor: vibe / mvp / production)

aspis mode <vibe|mvp|production> sets the project's default mode (aspis mode shows the current one).

Policy config (hooks, secrets, conventions)

Edit the data file under .aspis/config/policy/ — e.g. add a secret pattern to hooks.yaml (secrets:), change enforcement:, or adjust commit-convention.yaml. These are data: adding a rule is editing the file, not code.

Stack / project facts

Stack and goal live in .aspis/config/project.yaml and AGENTS.md (set at bootstrap). Change them deliberately, then refresh the brain with aspis context.

How a change reaches you

A config request can arrive user → project-lead → system-lead (the lead routes it) or user → system-lead directly — both are first-class. Understand the request, make the smallest correct change via the commands above, validate with aspis doctor, and hand any commit to the committer.

Plus depuis ce dépôt

même dépôt

commit-splitting

mahmoud-emad-dev/aspis

Keep commits atomic — split a mixed change set into scoped, reviewable commits.

2026-07-012

project-onboarding

mahmoud-emad-dev/aspis

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.

2026-06-292

architecture-memory

mahmoud-emad-dev/aspis

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.

2026-06-292

dependency-audit

mahmoud-emad-dev/aspis

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.

2026-06-272

clean-tree-precondition

mahmoud-emad-dev/aspis

Every editing agent should start on a clean working tree so parallel work never collides.

2026-06-272

commit-readiness

mahmoud-emad-dev/aspis

Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.

2026-06-272

name	config-management
description	How the System Lead safely changes project configuration — model routing, build mode, policy config, and stack — only through the aspis commands and the config data files, never by hand-editing a rendered runtime agent. Reachable user → project-lead → system-lead, or user → system-lead directly.

Config management

Model routing (which model each agent uses)

See what's available: aspis models --available — the valid provider/model ids for this machine.
Edit the data, not the agents:
- one tier for everyone → .aspis/config/models.yaml (the tier → model map);
- one agent → .aspis/config/agent-models.yaml (per-agent pin; aspis models --sync (re)generates it).
Make it live: aspis models --sync --apply — refresh the editable file, then re-render the agents.

Build mode (rigor: vibe / mvp / production)

aspis mode <vibe|mvp|production> sets the project's default mode (aspis mode shows the current one).

Policy config (hooks, secrets, conventions)

Stack / project facts

Stack and goal live in .aspis/config/project.yaml and AGENTS.md (set at bootstrap). Change them deliberately, then refresh the brain with aspis context.