Implement Specs
Build the feature from approved PRODUCT.md and TECH.md, keeping specs in sync
- What
- Build the feature from approved PRODUCT.md and TECH.md, keeping specs in sync
- Cost
- Free
- Needs
- approved PRODUCT.md and TECH.md specs (ideally written with the sibling Warp skills)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the implementation step of Warp's spec-first workflow: after PRODUCT.md and TECH.md are approved, build the feature treating the product spec as the source of truth for behavior and the tech spec as the source of truth for architecture — and keep the specs updated in the same PR as the implementation evolves, so review stays anchored to what will actually ship. Offers optional aids for large features (a PROJECT_LOG.md checkpoint file, a DECISIONS.md record). By @warpdotdev, listed here with credit to its creator. Honest caveats: built around Warp's conventions — adapt the `specs/` layout to your project; don't skip the "specs approved" prerequisite or you get implementation-first with extra paperwork. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: approved PRODUCT.md and TECH.md specs (ideally written with the sibling Warp skills) Install "Implement Specs" for me. Build the feature from approved PRODUCT.md and TECH.md, keeping specs in sync Repository: https://github.com/warpdotdev/common-skills/blob/main/.agents/skills/implement-specs/SKILL.md 1. Fetch the SKILL.md file for the warpdotdev-implement-specs skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "warpdotdev-implement-specs". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.