Draft and refresh PRD, TECH_SPEC, and ACTION_PLAN artifacts before implementation.
npx skills add https://github.com/Kbediako/CO --skill docs-first
Please help me install this Agent Skill. Skill: docs-first Source: https://github.com/Kbediako/CO/tree/main/skills/docs-first Command: npx skills add https://github.com/Kbediako/CO --skill docs-first
This skill streamlines the creation and maintenance of spec-driven work artifacts (PRD, TECH_SPEC, ACTION_PLAN) and their linkage to task registries, ensuring alignment before implementation.
Use this skill to draft or refresh PRD, TECH_SPEC, and ACTION_PLAN for a new task, then register and harvest checklists for review before coding.
High-intent search queries and answers about installing and using this skill.
You generate a PRD and TECH_SPEC before coding by using templates to draft or refresh product requirements and technical specifications, capturing user intent and linking them directly to task registries for alignment.
The best way to link a TECH_SPEC to a task registry is to generate the spec under tasks/specs, register it in tasks/index.json, and mirror the checklist to .agent/task/ to maintain machine-readable artifacts.
A docs-review step in spec-driven planning works by harvesting the generated ACTION_PLAN and task checklists to validate requirements and document reviews before any implementation execution begins.
You do not need to update docs/TASKS.md manually when creating an ACTION_PLAN, because the process automatically creates and refreshes the task checklist while mirroring updates directly to the task index.
You can use templates to refresh an existing PRD for a new task by re-evaluating the user request translation, updating the intent, and regenerating the linked specifications and action plans.
You need spec-driven artifacts in product development when workflows require strict alignment, meaning specifications must be drafted, linked to tasks, and reviewed before implementation begins.
pipecrew-aiScaffold new Git repositories from project briefs with tech stack defaults.
ArvorCoGenerate dependency-ordered user stories and tasks from spec.md and plan.md.
MiDouTechSyncs doc/index.yml with doc/guide.list.directory.md and updates from Markdown files.
vivainioManage spec-driven design workflows by organizing plans and requirements in a `specs/` directory.
