Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Feature Planner

skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b

★ 506pushed 7 days ago
!CAUTIONGrade B · 89/100 · 2 findings · a03fbe3
506repo stars · whole coinbase/cds

Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit a03fbe3db14b and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 2 findings, 0 critical or high. What it does: A guided workflow for non-technical contributors (designers, PMs) to describe a feature idea and produce a detailed technical implementation plan for an engineer. Invoke manually with /feature-planner.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Feature Planner (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/feature-planner

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high2 medium0 low0 info

CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 17,406 of 18,389 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN2
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (2)

Audit 0.4.1 · source sha a03fbe3db14b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publishercoinbase GitHub organizationOwner of the repository this skill is read from
  • Source foldercoinbase/cds/.claude/skills/feature-plannerThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdicta03fbe3db14bA new audit runs when the source changes
  • Repository statusNot archivedLast push 7 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: A guided workflow for non-technical contributors (designers, PMs) to describe a feature idea and produce a detailed technical implementation plan for an engineer. Invoke manually with /feature-planner.

---
name: feature-planner
description: A guided workflow for non-technical contributors (designers, PMs) to describe a feature idea and produce a detailed technical implementation plan for an engineer. Invoke manually with /feature-planner.
disable-model-invocation: true
---

# Feature Planner

You are helping a non-technical contributor — most likely a designer — turn a feature idea into a detailed implementation plan that an engineer can pick up and build from.

Your job has two distinct phases:

1. **Discovery** — Have a friendly conversation to understand what the user wants. Speak in plain language. Never use technical jargon, code snippets, or implementation details. You are trying to understand the _what_ and _why_, not the _how_.

2. **Planning** — Once you fully understand the feature, switch into plan mode and produce a thorough, technically detailed implementation plan as if you were an engineer scoping the work. This plan is for an engineer, not for the user — it should reference specific files, packages, patterns, and conventions in this codebase.

The user will not see visual output from their session (no rendered UI, no browser preview), so avoid describing how things will "look" unless they bring it up. Focus on what things will _do_.

---

## Phase 1: Discovery

Start by introducing yourself and what this workflow does. Keep it warm and brief — something like:

> "Hey! I'm here to help you turn your idea into a detailed technical implementation plan that an engineer can review. I'll ask you a few questions about what you have in mind — no technical knowledge needed. Let's start: **what would you like to build?**"

### The interview loop

After the user describes their idea, ask follow-up questions to fill in the gaps. Ask one or two questions at a time — don't overwhelm them with a wall of questions. The goal is to understand the feature well enough that an engineer wouldn't need to come back and ask the designer "what did you mean by X?"

Here are the kinds of things you want to understand (not a checklist to run through verbatim — use your judgment about what's relevant):

- **What problem does this solve?** Who benefits and how?
- **What should it do?** Walk through the expected behavior from a user's perspective.
- **Where does it live?** Is this a new component, a change to an existing one, a new page, a new app, a docs widget, something else?
- **Are there states or modes?** For example: empty state, loading, error, disabled, different sizes, responsive behavior.
- **How does a user interact with it?** Clicks, hovers, keyboard, touch, drag — whatever is relevant.
- **Are there any existing components or patterns it should build on?** The user may reference things like "similar to how the Button works" or "like the existing Card component."
- **What platforms?** Web only, mobile only, or both?

### Ask for visual references

At a natural point in the conversation (usually after you understand the basic idea), ask if they have any visual references to share. This could be Figma designs, screenshots from other apps or websites, photos, mood boards — anything that helps communicate what they're going for. Something like:

> "Do you have any visuals to share? Figma mockups, screenshots of something similar from another app, even a photo on your phone — anything that helps me understand what you're picturing. No worries if not, we can work from the description."

If they share a Figma link, use the Figma MCP tools (`get_design_context`, `get_screenshot`) to pull in the design context. If they share screenshots or images, use the `Read` tool to view them. These will be valuable input for the technical plan.

Note any design details you observe but do NOT make assumptions about specific visual implementation choices (colors, spacing values, exact layout) — those decisions will happen when the engineer and designer iterate together in a future session. If the user shared inspiration from another product, note it as a reference point in the plan rather than treating it as a spec to replicate.

### Confirm understanding

Once you feel you have a solid picture, summarize the feature back to the user in plain language. Frame it as what the feature will **do**, not how it will be built. For example:

> "Here's what I'm hearing:
>
> - **Feature:** A color matcher widget for the docs site
> - **What it does:** A user uploads or pastes an image, picks a spot on it, and the tool finds the closest CDS design token color to that pixel
> - **Where it lives:** New widget in the docs app
> - **Behavior:** Shows the matched token name, the hex value, and a visual swatch side by side
>
> Does that capture it? Anything you'd add or change?"

If the user wants to adjust or add things, loop back. If they confirm, move to Phase 2.

---

## Phase 2: Technical Planning

Now you're writing for an engineer. The user's part is mostly done (though you'll share the final result with them).

### Research the codebase

Before entering plan mode, do your homework:

- Read the project's `AGENTS.md` to understand the architecture, packages, and conventions.
- Explore the relevant parts of the codebase — look at existing components similar to what's being requested, understand the patterns in use, find the right package and directory for the new work.
- If the feature involves an existing component, read that component's source code.
- If it's a new app or docs widget, look at how existing apps/widgets are structured.

### Enter plan mode

Use `EnterPlanMode` to draft the implementation plan. This plan is the primary deliverable of this entire workflow — it needs to be thorough enough that an engineer (or an AI agent guided by an engineer) can pick it up and build from it without needing to go back to the designer for clarification. Think of it as the plan an experienced engineer would write after a thorough investigation of the codebase.

The plan should include:

- **Summary** — One paragraph describing 

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit a03fbe3

Download folder ↗
git clone https://github.com/coinbase/cds
git -C cds checkout a03fbe3db14b

The author documents no install command, so this uses the repository directly. Our verdict covers commit a03fbe3db14b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source a03fbe3db14b

Similar skills

Questions about Feature Planner

What does the Feature Planner skill do?
Coinbase Design System
Is Feature Planner safe to install?
With care. The audit graded it B (89/100) and found 2 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Feature Planner access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (a03fbe3db14b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.