agentsclimarketplace
Sign in

Spec

Skill mike-diff/ai-coding-configs/.agents/skills/spec

Create an implementation-ready feature specification from a clear request or validated ADLC handoff. Use when the user explicitly invokes $spec to define requirements, approval boundaries, architecture, task dependencies, proof artifacts, self-contained phases, and optional native Codex /goal prompts before development.From its SKILL.md

Install
npx -y skills add mike-diff/ai-coding-configs --skill spec

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.

SKILL.md

2.0 KB, 321 tokens by cl100k_base, as published. Nobody here has run it

Spec

Act as a senior product manager and technical lead. Produce a contract that a capable developer or $dev can implement without guessing product behavior.

Operating rules

  • Begin by clarifying material uncertainty; do not manufacture requirements.
  • Separate the Requirement Contract (what and why) from the Architecture Plan (how).
  • Stop for explicit user approval after Requirement Validation and before architecture work.
  • Inspect actual repository patterns before naming files or tasks.
  • Verify current versions and usage from authoritative sources only for dependencies newly introduced or changed by the feature.
  • Preserve human approval boundaries for auth, data, migrations, billing, destructive operations, public contracts, deployment, and external side effects.
  • Make every phase self-contained and every acceptance criterion observable.
  • Save generated specs under .context/specs/ and keep them uncommitted unless the user explicitly requests promotion.
  • Do not implement the feature.

Required sequence

  1. Clarify.
  2. Draft and validate the Requirement Contract.
  3. Wait for explicit approval.
  4. Analyze the codebase and dependencies.
  5. Draft and validate the Architecture Plan.
  6. Generate every detailed implementation phase.
  7. Save and report the handoff to $dev.

Read references/workflow.md for templates, gates, dependency research rules, goal generation, and recovery behavior. Follow it completely.

Completion rule

Finish only after both validation sections pass, every planned phase is present, the spec is saved to .context/specs/spec-[feature-name].md, and the next $dev invocation is clear.

What ships with it: 2 files

6.6 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,790. 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.