implementation-spec

implementation-spec is a skill for Claude Code from rshankras/claude-code-apple-skills. It costs 36 tokens per session (8,442 once invoked), scanned A, original, MIT.

A coordinating workflow that creates a complete set of product, architecture, interface, implementation, testing, and release specifications.

In plain words
What is it for?
Use it to turn an approved product plan into a coordinated specification package ready for implementation.
Why use it?
It keeps the documents produced by different development roles consistent with one another.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the apple-skills plugin — 147 skills shipped together , and of apple-skills

Good fit Use it to turn an approved product plan into a coordinated specification package ready for implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rshankras/claude-code-apple-skills/implementation-spec
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add rshankras/claude-code-apple-skills --skill implementation-spec
Clone the repo
git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills

Made for: Claude Code.

Or install apple-skills, the plugin that ships this one along with the rest of its 147 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for implementation-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/implementation-spec/github.svg)](https://agentmods.dev/skills/rshankras/claude-code-apple-skills/implementation-spec)
Your own site
<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/implementation-spec"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/implementation-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for implementation-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/implementation-spec"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/implementation-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,442 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 320
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Excessive Agency · line 996
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.08442
Opus 5.5 $0.00014 $0.03377
Sonnet 5.5 $0.00007 $0.01688
Haiku 4.5 $0.00004 $0.00844

Measured 1mo ago against content hash edfee0cecfd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implementation-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/product/implementation-spec/SKILL.md · 1,126 lines

How it starts

The opening of the file, as written. The whole thing — 1,126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementation Specification Orchestrator Skill

Master orchestrator that generates complete implementation specifications by coordinating all role-based agents.

Metadata

  • Name: implementation-spec
  • Version: 1.0.0
  • Role: Master Orchestrator
  • Author: ProductAgent Team

When This Skill Activates

This skill activates when the user says:

  • "generate implementation specifications"
  • "create implementation specs"
  • "generate all specs"
  • "create development specifications"
  • "generate complete specifications"

Description

You are the Master Implementation Specification Orchestrator. Your role is to coordinate all role-based agents (Product Manager, Architect, Designer, Developer, QA Engineer, Release Manager) to transform a product development plan into a complete, actionable set of implementation specifications.

You orchestrate the entire specification generation workflow, ensuring consistency across documents, pausing for user approval at critical decision gates, and producing a comprehensive specification package ready for implementation.

Prerequisites

Before activating this skill, ensure:

  1. A product development plan exists (from the product-agent skill)
  2. The plan includes: problem analysis, MVP scope, positioning, ASO optimization
  3. User has reviewed and approved the product development plan
  4. User is ready to proceed to detailed specification generation

Optional but Recommended (enhances specification quality): 5. Competitive analysis (from competitive-analysis skill or product plan) 6. Market research (from market-research skill or product plan)

Input Sources

  1. Product development plan (typically product-plan-*.md)

    • Generated by the product-agent skill
    • Contains: problem analysis, MVP scope, positioning, ASO optimization
    • Located in project root
  2. User decisions at each phase gate:

    • Approval to proceed
    • Requested changes or iterations
    • Preferences and clarifications

Workflow

Read the full file on GitHub · 1,126 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 1,126 lines · 36 tokens per session scan A edfee0cecfd0

Subscribe to this mod's changes

implementation-spec is a skill published in the GitHub repository rshankras/claude-code-apple-skills (816 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 8,442 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

customer-success

Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.

travisjneuman/.claude · 47 tokens

event-planner

Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.

travisjneuman/.claude · 37 tokens

hr-talent

HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.

travisjneuman/.claude · 47 tokens

operations

Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.

travisjneuman/.claude · 45 tokens

process-flowchart-designer

Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.

travisjneuman/.claude · 37 tokens

scaffold

Project scaffolding - generate boilerplate for common project types with best-practice defaults. Use for: scaffold, boilerplate, template, new project, init, create project, starter, setup, project structure, directory structure, monorepo, microservice, API template, web app template, CLI tool template, library…

0xDarkMatter/claude-mods · 69 tokens