Verified:GitHub

oat-project-promote-spec-driven

Backfill missing discovery, spec, and design artifacts to promote projects to spec-driven mode.

1|Updated Jan 26, 2026

Search Tags:#project management #workflow automation #spec-driven development #project lifecycle #artifact generation #oat

Ready to run

npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-promote-spec-driven

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oat-project-promote-spec-driven
Source: https://github.com/tkstang/open-agent-toolkit/tree/main/.agents/skills/oat-project-promote-spec-driven
Command: npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-promote-spec-driven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables projects currently using simpler workflows (quick or import) to adopt the full Spec-Driven lifecycle, ensuring better structure and rigor without recreating the project.

Core Features & Use Cases

Backfills Missing Artifacts: Automatically generates discovery.md, spec.md, and design.md if they are missing.
Preserves History: Ensures existing plan.md and implementation.md are not overwritten, maintaining project provenance.
State Transition: Updates the project's state to spec-driven mode, aligning it with OAT's structured lifecycle.
Use Case: A project was initially set up with a quick import. Now, to meet compliance or quality standards, it needs the full discovery, spec, and design documentation. This skill seamlessly transitions it.

Quick Start

Promote the current active project to the spec-driven lifecycle.

Frequently Asked Questions about oat-project-promote-spec-driven

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I transition an existing project to a spec-driven development workflow?▼

To transition to a spec-driven development workflow, this skill backfills missing discovery, spec, and design artifacts in place while preserving existing plan and implementation history, updating project state metadata to enforce full lifecycle rigor.

Can I upgrade a quick import project to spec-driven rigor without recreating it?▼

Yes, you can upgrade a quick import project to spec-driven rigor without recreating it. The skill generates missing discovery.md, spec.md, and design.md files automatically while preserving existing project provenance.

What is backfilling missing artifacts in project lifecycle management?▼

Backfilling missing artifacts in project lifecycle management is generating required documentation like discovery.md, spec.md, and design.md post-initialization to enforce compliance and align projects with a structured spec-driven state.

Will promoting to spec-driven mode overwrite my existing plan.md file?▼

No, promoting to spec-driven mode will not overwrite your existing plan.md file. The skill explicitly preserves existing plan and implementation history while only generating missing discovery, spec, and design artifacts.

When do I need to adopt spec-driven project management for compliance?▼

You need to adopt spec-driven project management for compliance when a project initially set up with a quick import requires full discovery, spec, and design documentation to meet quality standards without recreating the project.

Does workflow automation support backfilling project artifacts in place?▼

Yes, workflow automation supports backfilling project artifacts in place. This skill seamlessly transitions project state metadata to spec-driven mode by generating missing documentation while maintaining existing implementation files.