speckit-tinyspec-implement

To automate tinyspec task execution, provide the tinyspec file path to apply planned tasks to your codebase. The skill reads the file, modifies code in order, verifies completion, and updates the tinyspec status to done.

The best way to implement tinyspec tasks is using automated end-to-end execution that parses the file, loads context data, and modifies code sequentially. This reduces manual effort and prevents drift between the plan and the actual codebase.

Yes, you need a .specify directory to run tinyspec-based code modifications. This skill is applied to projects using the spec-kit workflow, relying on that directory structure to locate and interpret tinyspec files correctly.

Automated tinyspec implementation tracks task progress by executing tasks in their defined order and verifying completion at each step. Once all planned tasks are successfully applied and verified, it updates the tinyspec file status to done.

Spec-kit workflows require manual steps when tinyspec plans are not automated. Applying an automation skill reads the tinyspec files directly and applies the planned tasks to the project, eliminating the manual translation and reducing code drift.