# Speckit Implement > Implement the current concise Spec Kit plan by executing the Work Checklist in plan.md. Use when this capability is needed. - Skill: `tomevault-io/speckit-implement-2` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/speckit-implement-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/speckit-implement-2/raw - Safety review: pending - 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/speckit-implement-2 --- # Implement From Plan Use `plan.md` as the source of truth. Separate `tasks.md` files are legacy and are not required. ## Workflow 1. Run `.specify/scripts/powershell/check-prerequisites.ps1 -Json` and read the active `plan.md`, `.specify/memory/constitution.md`, and `AGENTS.md`. 2. Extract the `Work Checklist`, package surfaces, verification commands, and open questions from the plan. 3. If an open question blocks correctness, ask it before editing. Otherwise make conservative assumptions and proceed. 4. Implement checklist items in dependency order. Update the checkbox in `plan.md` as each item is completed. 5. Keep changes scoped to files named or implied by the plan and constitution. 6. For public API changes, apply `openspecy-design-public-api` before editing signatures. 7. Run staged verification with `openspecy-run-quality-gates`: focused tests, relevant benchmarks, toolchain preflight and documentation, full tests, then package check. Report skipped long-running, external-resource, optional backend, or CI-only checks precisely. ## Rules - Tests cover current package behavior; old implementations used for speed comparisons belong in `benchmarks/`. - Same-output function improvements need a benchmark update or a written reason in the plan. Short benchmarks need repeated measurements and must flag material regressions. - Do not edit `NAMESPACE`, `man/*.Rd`, or generated pkgdown HTML directly. - Do not regenerate documentation with a roxygen2 version that differs from the version configured in `DESCRIPTION`. - Preserve `OpenSpecy` object structure, identifiers, metadata alignment, and relevant attributes through function flows. - Do not add Shiny application code to this package repository. --- > Source: [wincowgerDEV/OpenSpecy-package](https://github.com/wincowgerDEV/OpenSpecy-package) — distributed by [TomeVault](https://tomevault.io).