agentsclimarketplace

Feature development

Skill wchen02/cursor-agent-learning/.cursor/skills/feature-development

A hands-on project to learn Cursor’s agent customization: rules, skills, subagents, commands, hooks, and AGENTS.md. Everything is set up with examples and docs so you can try things and tweak them.

Install
npx -y skills add wchen02/cursor-agent-learning --skill feature-development

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implements a feature using plan → implement → verify. Use when the user wants to add a new feature with a clear plan and verification.

SKILL.md

1.4 KB, as published. Nobody here has run it

Feature Development Framework

This skill runs a feature development workflow: plan first, implement, then verify.

Steps

  1. Plan

    • Invoke the planner subagent with the user’s feature description (or the current conversation context).
    • Capture the output: scope, numbered steps, dependencies, notes. Do not write code yet.

  2. Implement

    • Implement the steps from the plan. Follow project rules (e.g. @general-conventions, @api-conventions or @typescript-patterns when relevant).
    • If the user asked for “first N steps only,” implement only those and say what’s left for later.
    • Prefer small, incremental changes; run or mention tests where applicable.

  3. Verify

    • Invoke the verifier subagent to confirm:
      • The implementation matches what was planned.
      • Relevant tests pass (or are added and pass).
      • No obvious gaps or regressions.
    • Summarize verification results for the user. If the verifier found issues, address them or list them clearly.

Notes

  • If the user only asked for a plan, stop after step 1 and present the plan.
  • If the user says “skip verification,” do steps 1–2 only and say verification was skipped.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.