agentsclimarketplace

Wr spec

Skill nbsp1221/wayrail/template/.agents/skills/wr-spec

🧭 Personal toolkit for repo-local AI agent workflows

Install
npx -y skills add nbsp1221/wayrail --skill wr-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.
  • 0 stars0 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

Use when starting or creating a new wayrail spec item from a feature idea, bug, research task, or workflow change. Scaffolds specs/<YYYYMMDD-HHMM-short-slug>/ with spec.md, plan.md, verification.md, and review.md, then authors the spec-stage problem, scope, requirements, success criteria, assumptions, and planning handoff. Do not use for implementation planning, code execution, verification, review, or editing an existing spec item.

SKILL.md

2.3 KB, 410 tokens by cl100k_base, as published. Nobody here has run it

wr-spec

Start a new wayrail spec item.

Use When

  • The user asks to start, create, scaffold, open, or draft a new spec.
  • The input is a feature idea, bug, research task, workflow change, or unclear work item that needs spec-stage framing.
  • The user directly invokes $wr-spec.

Do Not Use When

  • The user asks to plan implementation; use the plan stage instead.
  • The user asks to implement code.
  • The user asks to verify, review, or complete later lifecycle stages.
  • The user asks to edit an existing spec item unless they explicitly want a new spec item.

Compatibility

This is a repo-local wayrail skill. Use it only in repositories that contain the wayrail starter structure, including specs/_templates/. If that structure is missing, stop and report that the project has not been initialized for wayrail instead of inventing files by hand.

Workflow

  1. Determine a clear spec title and a short lower-case slug from the user request.
  2. Run scripts/new-spec-item before writing prose.
  3. Prefer --json; pass --slug, --root, and --timezone when the values are known.
  4. Read the JSON output and open the generated spec.md.
  5. Fill only spec.md with spec-stage content.
  6. Leave plan.md, verification.md, and review.md as stubs for later lifecycle stages.

Spec Authoring Rules

  • Capture the problem, why now, scope, non-goals, requirements, success criteria, assumptions, and planning handoff.
  • Make reasonable defaults explicit.
  • Ask the user only for decisions that materially change scope, product behavior, or success criteria.
  • Classify open questions as blocking before planning or deferred to planning.
  • Do not include implementation plans, code changes, test commands, or review conclusions.

Completion

Report the created spec path and recommend the plan stage as the next action.

What ships with it: 2 files

14.3 KB alongside SKILL.md, 1 of them executable

agents/

scripts/

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.