Specdd Adopt
Apps & Automationspecdd-adoptSpecdd Adopt is an Agent Skill for apps & automation published in the aiskillstore/marketplace repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when Agent needs to add SpecDD to a project or update SpecDD framework files through the CLI before normal SpecDD work begins.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/aiskillstore/marketplace/blob/HEAD/skills/specdd/specdd-adopt/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/specdd-adopt, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
SpecDD Adopt
Use this skill to help a repository adopt SpecDD through the specdd CLI.
If .specdd/bootstrap.md already exists, use this skill only for operator-requested framework bootstrap updates; use specdd-author for spec authoring or another task-specific SpecDD skill.
Workflow
- Check whether the target repository already has
.specdd/bootstrap.mdor existing.sddcontracts. - If no bootstrap exists and the operator asked to add SpecDD, use the
specdd-cliskill and thespecddCLI to initialize bootstrap files. - If bootstrap files exist and the operator asked to update SpecDD framework files, use the
specdd-cliskill and thespecddCLI to update them. - If the CLI is unavailable, report that setup or update is blocked until the CLI is available.
- After CLI initialization, and after CLI update only when framework files changed, read the active bootstrap chain before proposing or creating local
.sddspecs. - If the target is already a SpecDD project and the operator did not ask for framework updates, switch to
specdd-authoror the relevant task-specific skill. - Inspect only the repo shape needed for initial boundaries: top-level directories, docs, manifests, tests, and major entry points.
- Propose the smallest useful initial shape, usually a root project spec before narrower child specs.
- Create
.sddfiles only when the user explicitly requested or approved that adoption scope.
Adoption Rules
- Use the CLI to add or update SpecDD framework bootstrap files when the operator asks for setup or framework updates.
- Do not manually install, update, edit, or copy SpecDD framework bootstrap files outside the CLI.
- Do not change implementation files unless the user explicitly asks for implementation work too.
- Use path-based ownership, explicit
References, andCan modifyorOwnsto make proposed authority discoverable. - Include only sections that add useful local authority, constraints, behavior, tasks, or context.
- Do not present guessed behavior as an active contract; label assumptions or ask for confirmation.
- Keep proposed or created specs short, local, behavioral, and constraint-oriented.
Reporting
Report whether the repository was already bootstrapped, CLI setup or update status, the adoption scope, specs proposed or created, and any setup left to the user.