# Spec Artifacts

> Use when a task needs a specific specification, decision, contract, release note, or handoff format.

- Skill: `jukrap/spec-artifacts` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jukrap/spec-artifacts`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jukrap/spec-artifacts/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jukrap (https://skillmd.com/u/jukrap)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jukrap/spec-artifacts

---


# Specification Artifacts

Produce only the requested artifact. Reuse the project's format and existing evidence; do not require a planning ceremony, fixed reading chain, or all artifact types.

Keep intended requirements distinct from current implementation. Identify the relevant repository or registered workspace members and the existing record destination; shared records do not authorize code or Git operations across members. Preserve local-only rules and user approval conditions.

Read `references/formats.md` for the selected artifact's fields. Preserve public API, data, version, and migration constraints when relevant. Record only verification actually performed. Detailed domain examples are optional in the repository reference library, not mandatory prerequisites.

For a long independent artifact, an optional delegated DRAFT must use bounded evidence and short relevant history. The parent reviews protected facts and unknowns before adoption; ordinary artifacts stay in the main task.