canon-spec-publishing

Estrellas14

Forks0

Actualizado24 de febrero de 2026 a las 19:32

Promote a task artifact pack into a canonical spec under /docs/specs or /docs/architecture/specs, following /docs/spec-guide.md lifecycle (active-only, delete replaced). No writes without APPROVE.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

artemiv4nov

artemiv4nov/fabricator

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1211

SKILL.md

readonly

name	canon-spec-publishing
description	Promote a task artifact pack into a canonical spec under /docs/specs or /docs/architecture/specs, following /docs/spec-guide.md lifecycle (active-only, delete replaced). No writes without APPROVE.

canon-spec-publishing

Purpose

Turn stable knowledge from WORK_PATH into a canonical spec in /docs/**.

Inputs

WORK_PATH (absolute)
Spec kind: product | architecture
Target: update existing canonical spec OR create a new one

Output

Created or updated canonical spec file in /docs/specs/ or /docs/architecture/specs/
Updated spec index README (if present)

Constraints

Read /docs/spec-guide.md if present and follow it as the single source of truth. If absent: apply default conventions (self-contained canonical spec, active-only, delete replaced specs, rely on git history for old versions).
Keep only active specs in /docs/** (delete replaced specs, rely on git history).

Internal loop

Grounding:
- Read /docs/spec-guide.md if present
- Read relevant /docs/**/specs/README.md index if present
- Read WORK_PATH artifacts (requirements/tech-spec/contracts/models/evidence)
Decide publish target:
- Search for an existing canonical spec that matches the same domain.
- If found: propose an update-in-place.
- If not found: propose a new NNN-short-title.md in the correct folder. Compute NNN:
  - List all NNN-*.md files in the target folder.
  - next = max(NNN from existing files) + 1; zero-pad to 3 digits.
  - If no numbered files exist, start at 001.
  - Propose the full path; do not create until APPROVE.
Compose canonical spec:
- Canonical spec must be self-contained.
- It may summarize contracts/models and link to stable internal docs if needed.
- Do not copy volatile check outputs; keep checks at repo-level.
Coherence gate:
- If contradictions with existing canonical specs exist, stop and propose resolution.
- Update spec index README if it exists.

Completion criteria

Canonical spec created or updated in /docs/**
No contradictions with existing specs

Return control to Fabricator.

Más de este repositorio

mismo repositorio

bitbucket-tooling

artemiv4nov/fabricator

Use after git-tooling push to create or manage a PR on Bitbucket Server. Composes PR description, creates PR via API, handles review comments. Terminal delivery step. (5 supporting files)

2026-03-0414

jira-tooling

artemiv4nov/fabricator

Use at session start to pull Jira issue details into context, or post-delivery to create/update issues. Integrates with task-authoring (issue → task.md) and git-tooling (commit links). (2 supporting files)

2026-03-0414

artifact-selection

artemiv4nov/fabricator

Select the minimal sufficient artifact set (task/requirements/tech-spec/contracts/models/verify/evidence) for the current change, and recommend the next skills. Use after task intake or when scope/risk changes.

2026-02-2414

contract-design

artemiv4nov/fabricator

Define interface/persistence contracts (APIs, schemas, deeplinks, storage formats) + compatibility rules. Use when public surfaces or stable formats are involved.

2026-02-2414

implementation

artemiv4nov/fabricator

Implement changes guided by existing artifacts and repo conventions (AGENTS/README/DEVELOPMENT + WORK_PATH). Make small diffs, follow coherence gate, and optionally trigger verification-run.

2026-02-2414

model-design

artemiv4nov/fabricator

Model states/flows/invariants for complex behavior (async, retries, caching, offline). Use when correctness depends on state machines or non-trivial flows.

2026-02-2414

canon-spec-publishing

Purpose

Turn stable knowledge from WORK_PATH into a canonical spec in /docs/**.

Inputs

WORK_PATH (absolute)

Spec kind: product | architecture

Target: update existing canonical spec OR create a new one

Output

Created or updated canonical spec file in /docs/specs/ or /docs/architecture/specs/

Updated spec index README (if present)

Constraints

Read /docs/spec-guide.md if present and follow it as the single source of truth. If absent: apply default conventions (self-contained canonical spec, active-only, delete replaced specs, rely on git history for old versions).

Keep only active specs in /docs/** (delete replaced specs, rely on git history).

Internal loop

Grounding:

Read /docs/spec-guide.md if present
Read relevant /docs/**/specs/README.md index if present
Read WORK_PATH artifacts (requirements/tech-spec/contracts/models/evidence)

Decide publish target:

Search for an existing canonical spec that matches the same domain.
If found: propose an update-in-place.
If not found: propose a new NNN-short-title.md in the correct folder. Compute NNN:
- List all NNN-*.md files in the target folder.
- next = max(NNN from existing files) + 1; zero-pad to 3 digits.
- If no numbered files exist, start at 001.
- Propose the full path; do not create until APPROVE.

Compose canonical spec:

Canonical spec must be self-contained.
It may summarize contracts/models and link to stable internal docs if needed.
Do not copy volatile check outputs; keep checks at repo-level.

Coherence gate:

If contradictions with existing canonical specs exist, stop and propose resolution.
Update spec index README if it exists.

Completion criteria

Canonical spec created or updated in /docs/**

No contradictions with existing specs

Return control to Fabricator.