메뉴
REASONS Canvas spec schema (8 sections + closed frontmatter, profiles A/B). Trigger: when authoring, reviewing or validating a spec in `sdd.schema: reasons` mode.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | aiws-sdd-spec-schema |
| description | REASONS Canvas spec schema (8 sections + closed frontmatter, profiles A/B). Trigger: when authoring, reviewing or validating a spec in `sdd.schema: reasons` mode. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
Closed specification schema for sdd.schema: reasons (auditable enterprise apps). The spec is the
single source of truth; code derives from it. Headings, frontmatter keys and enum values are English;
the body follows the project language.
spec_id (NNN), title, slug, version (vN), schema_version: 2.status (draft | user-reviewed | it-approved | implemented | retired), created, updated.owner (email), reviewers (list).profile (A | B), language (ca | es | en).handles_personal_data, requires_external_api, requires_authentication, estimated_complexity (S|M|L).serves_html_ui. Profile-B: uses_localstorage, uses_npm_build, uses_react, runs_node_server.apply_branding (default true). Relations: related_specs, tags.0. Changelog · 1. Requirements · 2. Entities · 3. Approach · 4. Structure · 5. Operations · 6. Norms · 7. Safeguards.
(Body prose in the project language; headings stay English.)
Maps to: line citing ≥1 acceptance criterion (§1.5).handles_personal_data: true → §7.2 (legal basis, retention, rights, DPO) is mandatory.runs_node_server: true.Stable specs in {{paths.specs}}/{NNN}-{slug}.md; in-flight work in {{paths.changes}}/. Versioning is Git
(history, PRs) — no _vN filename suffixes. Record status transitions in the spec's §0 Changelog.
status)draft → user-reviewed → it-approved → implemented → retired (linear; a reopen/audit-failure steps back one).
Gates: draft → user-reviewed needs the §8 checklist green + non-empty reviewers (owner sign-off, no
version bump); user-reviewed → it-approved needs all four sdd-audit-* green. Code and tests are
generated only from user-reviewed or later. The aiws-sdd-spec-review skill drives every transition and refuses
any not in this chain (e.g. draft → it-approved directly).
The full schema, worked examples and the controls catalogue (TECH/SEC/CONV) are an external reference (supply your own; not bundled here) — load them only when authoring or auditing. This skill is the working summary.
Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.
Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.
Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.
Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.
Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.
Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.