Remove the templates/skills folder

[shiroyasha]

Previously, this was used by an early version of a built in agent. This is no longer used. Update two things:

• Remove this folder
• Update the AGENTS.ms and cursor skills to not reference it anymore.

[superplane-leonardo]

🤖 Automated Issue Review

Here is a copy-pasteable GitHub review comment in Markdown:

---

Review: Remove the templates/skills folder (#4408)

Issue source

Fetched via the GitHub API. 0 comments on the issue, so there is no prior review cycle or human follow-up to incorporate.

Note on scope: The issue title and body say “AGENTS**.ms**” — that is almost certainly a typo for AGENTS.md, which is where the only in-repo reference to this path today lives.

---

1. Validity

Yes, the issue is valid and consistent with the repo state.

• The directory /templates/skills/ exists and contains six Markdown files, all under a DigitalOcean naming pattern (e.g. digitalocean.createDatabase.md, digitalocean.getDatabaseCluster.md).
• A full-text search for templates/skills shows only one hit in the tree: a bullet in AGENTS.md (see below). There are no references in application code, Makefiles, or docker-compose files in this snapshot.
• The stated rationale — legacy path for an old built-in agent — is plausible: nothing else in the repo points at this folder for runtime behavior.

Reproducibility: N/A for a “remove dead files” task; the folder is present and the guideline is the only live documentation tie-in.

Optional follow-up (out of issue scope for this review): docs/prd/ai-agent-component-skill-awareness.md describes per-component SKILL.md discovery; it does not reference templates/skills/, so it does not conflict with removal. If product intent is still “AI-assisted components need a skill,” implementers may later want a single replacement rule (e.g. per-integration SKILL.md or .cursor/) so contributors are not left with no pointer after the bullet is deleted.

---

2. Location in the codebase

What	Where
Folder to remove	templates/skills/ (six digitalocean.*.md files)
Doc that must be updated	AGENTS.md — the bullet that instructs creating/updating skill files under templates/skills/ (around line 37 in the current file)
Cursor skills	Under .cursor/skills/ (e.g. superplane-changelog, superplane-issue-logger, superplane-integration-research). Grep found no templates/skills references in .cursor/ in this workspace. If the product issue means “any Cursor-related doc,” a human should double-check Cursor project settings in the cloud/GitHub that are not in this repo.

No other templates/skills string matches were found in the working tree for this review.

---

3. Complexity and effort

• Complexity: simple — filesystem delete + one documentation line (and optionally a typo fix in the issue: AGENTS.ms → AGENTS.md when closing).
• Effort (technical, not calendar): On the order of minutes of focused work: delete seven paths (one directory + six files) or the folder in one go, one edit in AGENTS.md, then sanity-check with repo-wide search for templates/skills (and for “early agent” or “builtin” strings if you want to be thorough).

---

4. Duplicates

• No open duplicate found for “remove templates/skills” in the quick GitHub search used for this review.
• Older PRs/issues mentioning “skills” (e.g. expression/messaging skills, Cursor rules) are not the same as this legacy folder; treat as unrelated unless a maintainer links them.

---

5. Recommended approach

1. Delete templates/skills/ and its contents.
2. Edit AGENTS.md — remove the entire bullet that mandates templates/skills/<component-or-trigger>.md, or replace it with guidance that matches the current AI/component skill model (e.g. per-component SKILL.md under integrations, if that is the canonical place — align with docs/prd/ai-agent-component-skill-awareness.md and docs/contributing/ as needed; that alignment is a product decision, not required to satisfy “remove folder + stop referencing it”).
3. Re-grep the repository for templates/skills and for templates/skills/ to ensure zero stale references.
4. CI: Unlikely to need build/test changes; no Makefile references were found. Run your usual make check / lint if the team policy requires it for any doc change.

---

6. Human feedback from previous review

Not applicable — the issue has no comments and was not “returned” with threaded feedback. Nothing to address from prior review cycles in GitHub for this item.

---