spec-driven-init

Automate initial project documentation creation by structuring materials into a starter edition.

Updated Nov 12, 2017
One-click install
npx skills add https://github.com/ak110/dotfiles --skill spec-driven-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-init
Source: https://github.com/ak110/dotfiles/tree/main/plugins/agent-toolkit/skills/spec-driven-init
Command: npx skills add https://github.com/ak110/dotfiles --skill spec-driven-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial creation of a project's documentation by structuring current materials into a starter edition.

Core Features & Use Cases

  • Prepare initial documentation skeleton for existing projects to align terminology, structure, and templates.
  • Coordinate term usage and reference placement across docs/features and docs/topics.
  • Update code references to point to the current documentation paths during onboarding.

Quick Start

Run /agent-toolkit:spec-driven-init to generate the initial version of the project's documentation.

Frequently Asked Questions about spec-driven-init

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

FAQPage Schema
How do I generate a documentation skeleton for an existing project?

To generate a documentation skeleton for an existing project, you can run the /agent-toolkit:spec-driven-init command to automate structuring your current materials into a starter edition. This aligns terminology, structure, and templates across docs.

What is spec-driven documentation onboarding?

Spec-driven documentation onboarding is the process of preparing an initial documentation skeleton to align terminology and structure. It coordinates term usage, reference placement across docs/features and docs/topics, and updates code references to current documentation paths.

How do I align terminology and templates across project docs?

You align terminology and templates by structuring current materials into a starter edition. This coordinates term usage and reference placement across docs/features and docs/topics, and updates code references to point to the current documentation paths.

Can I use this to update code references during documentation onboarding?

Yes, during documentation onboarding, the process updates code references to point to the current documentation paths. This ensures that your codebase accurately reflects the newly structured documentation paths.

What are the frontmatter requirements for SKILL.md in spec-driven docs?

The frontmatter requirements for SKILL.md are enforced during the initial creation of project documentation. This ensures a clear activation workflow for manual or explicit invocation from the spec-driven system, maintaining structural consistency.