# Kbediako Co Docs First

> Docs-First (Spec-Driven)

- Skill: `tomevault-io/kbediako-co-docs-first` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/kbediako-co-docs-first`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/kbediako-co-docs-first/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/kbediako-co-docs-first

---


# Docs-First (Spec-Driven)

## Overview

Use this skill when a task needs a spec-driven workflow. The objective is to create or refresh PRD + TECH_SPEC + ACTION_PLAN + the task checklist before editing code or docs, capture a brief translation of the user’s request in the PRD for context retention, and keep task mirrors and review evidence in sync as understanding evolves.

## Global Adoption Defaults

For shipped CO usage, default to this command path unless task constraints say otherwise:
- `codex-orchestrator flow --task <task-id>`
- `codex-orchestrator doctor --usage --window-days 30 --task <task-id>`
- `codex-orchestrator rlm --multi-agent auto "<goal>"`

## Workflow

1) Draft or refresh PRD + TECH_SPEC + ACTION_PLAN
- PRD: capture intent and user-request translation (use `.agent/task/templates/prd-template.md`).
- TECH_SPEC: capture technical requirements (use `.agent/task/templates/tech-spec-template.md`; stored under `tasks/specs/<id>-<slug>.md`).
- ACTION_PLAN: capture sequencing/milestones (use `.agent/task/templates/action-plan-template.md`).
- Depth scales with scope, but all three docs are required.
- For low-risk tiny edits, follow the bounded shortcut in `docs/micro-task-path.md` instead of long-form rewrites (still requires task/spec evidence).

2) Register the TECH_SPEC and task
- Add the TECH_SPEC to `tasks/index.json` (including `last_review`).
- Create/refresh the task checklist (`tasks/tasks-*.md`) and mirror to `.agent/task/`.
- Update `docs/TASKS.md` with the snapshot entry.
- When you need machine-readable artifacts, use a consistent template or structured output format.

3) Run docs-review before implementation
- `npx codex-orchestrator start docs-review --format json --no-interactive --task <task-id>`
- If running in cloud mode, ensure the branch exists on remote. For local-only branches, set `CODEX_CLOUD_BRANCH=main` (or another pushed branch).
- Link the manifest path in the checklists.

4) Implement and validate
- Keep PRD/TECH_SPEC/ACTION_PLAN, checklists, and manifests aligned.
- Update PRD/TECH_SPEC/ACTION_PLAN when new constraints, risks, or scope changes are discovered during implementation.
- If docs are missing or stale, stop and request approval before proceeding.

## Output expectations
- PRD + TECH_SPEC + ACTION_PLAN + task checklist created/refreshed.
- TECH_SPEC linked in task registry and mirrors updated.
- Docs-review evidence captured before implementation.

## Related docs
- `docs/AGENTS.md`
- `docs/guides/instructions.md`

## Related skills
- `delegation-usage`: for task-scoped delegated research/review streams after docs scaffolding.
- `standalone-review`: for pre-implementation approval and implementation checkpoints.
- `elegance-review`: for post-implementation minimality pass before handoff.
- `agent-first-adoption-steering`: for non-blocking advanced-feature steering and option framing.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/kbediako) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->