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.
npx agentmods add skills/msapps-mobile/claude-plugins/notion-spec-to-implementationnpx skills add MSApps-Mobile/claude-plugins --skill notion-spec-to-implementationgit clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/msapps-mobile/claude-plugins/notion-spec-to-implementation)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/notion-spec-to-implementation.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01888 |
| Opus 5 | $0.00025 | $0.00944 |
| Sonnet 5 | $0.00010 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
notion-spec-to-implementation 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 6d 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.
This is a copy
100% identical to notion-spec-to-implementation — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec to Implementation
Transforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.
Quick Start
When asked to implement a specification:
- Find spec: Use
Notion:notion-searchto locate specification page - Fetch spec: Use
Notion:notion-fetchto read specification content - Extract requirements: Parse and structure requirements from spec
- Create plan: Use
Notion:notion-create-pagesfor implementation plan - Find task database: Use
Notion:notion-searchto locate tasks database - Create tasks: Use
Notion:notion-create-pagesfor individual tasks in task database - Track progress: Use
Notion:notion-update-pageto log progress and update status
Implementation Workflow
Step 1: Find the specification
1. Search for spec:
- Use Notion:notion-search with spec name or topic
- Apply filters if needed (e.g., created_date_range, teamspace_id)
- Look for spec title or keyword matches
- If not found or ambiguous, ask user for spec URL/ID
Example searches:
- "User Authentication spec"
- "Payment Integration specification"
- "Mobile App Redesign PRD"
Step 2: Fetch and analyze specification
1. Fetch spec page:
- Use Notion:notion-fetch with spec URL/ID from search results
- Read full content including requirements, design, constraints
2. Parse specification:
- Identify functional requirements
- Note non-functional requirements (performance, security, etc.)
- Extract acceptance criteria
- Identify dependencies and blockers
See reference/spec-parsing.md for parsing patterns.
Step 3: Create implementation plan
1. Break down into phases/milestones
2. Identify technical approach
3. List required tasks
4. Estimate effort
5. Identify risks
Use implementation plan template (see [reference/standard-implementation-plan.md](reference/standard-implementation-plan.md) or [reference/quick-implementation-plan.md](reference/quick-implementation-plan.md))
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/api-feature.md 13 KB
- examples/database-migration.md 2.4 KB
- examples/ui-component.md 1.6 KB
- reference/milestone-summary-template.md 456 B
- reference/progress-tracking.md 8.8 KB
- reference/progress-update-template.md 420 B
- reference/quick-implementation-plan.md 480 B
- reference/spec-parsing.md 6.8 KB
- reference/standard-implementation-plan.md 3.2 KB
- reference/task-creation-template.md 597 B
- reference/task-creation.md 7.8 KB
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.
- 6d ago First seen · 220 lines · 50 tokens per session scan A 28caed825f60
notion-spec-to-implementation is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed 10d ago), licensed MIT. It adds 50 tokens to every session and 1,888 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to notion-spec-to-implementation, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
project
AI 코워커 플러그인 패밀리('MoAI-Cowork, 모두의 코워크')의 프로젝트 초기화 단일 진입점. /project 로 진입한다 — Claude Cowork(Desktop) 작업을 담당하는 Desktop 슈퍼 오케스트레이터/어드바이저다. 소크라테스 인터뷰로 맥락을 파악하고, 설치된 플러그인 인벤토리를 스캔한 뒤, 프로젝트 전용 커스텀 에이전트와 스킬 체인을 설계해 AGENTS.md(폴더 지침 정본, ≤500라인)와 이를 @AGENTS.md로 불러오는 CLAUDE.md·.claude/agents/·.moai/ 스캐폴드를 생성한다. 이후 사용 중 신호를 감지하면…
collab-pm-report
한국 팀의 주간 비즈니스 리뷰(WBR) 보고서 자동 생성 스킬입니다. 일일 노트·완료 태스크·KPI 데이터를 입력받아 임원/팀 두 버전(격식체/구어체)으로 작성합니다. Notion·Linear·Asana·Slack MCP가 가용하면 자동 데이터 fetch, 없어도 자유 텍스트 입력 fallback. 다음과 같은 요청 시 반드시 이 스킬을 사용하세요: "주간보고 작성", "WBR 준비", "이번 주 한 일 정리" "주간 회의 자료", "위클리 리포트", "주간 업무 보고" "임원 주간보고", "팀 주간보고" [책임 경계] 제품 발견·로드맵/마일스톤 기획은…
hr-operations
원격 근무와 팀 운영 정책을 설계해주는 스킬입니다. "재택근무 정책 만들어줘", "협업 도구 추천해줘", "비동기 커뮤니케이션 가이드 만들어줘"처럼 말하면 됩니다. 원격·하이브리드 근무 정책, 협업 도구 선정 기준, 생산성 관리 프레임워크, 직원 경험 설계를 지원합니다.
hr-performance-review
성과평가 체계를 설계하고 실행을 도와주는 스킬입니다. "OKR 설정해줘", "성과 리뷰 템플릿 만들어줘", "피드백 면담 스크립트 써줘"처럼 말하면 됩니다. MBO·OKR·KPI 체계 구축, 360도 평가 설계, 인사 고과 가이드, 피드백 면담 스크립트 작성을 지원합니다.
collab-process
업무 프로세스를 문서화하고 표준화합니다. "SOP 만들어줘", "구매 요청서 써줘", "회의록 정리해줘", "운영 매뉴얼 작성해줘"라고 요청할 때 사용하세요. 운영 매뉴얼, SOP(표준 운영 절차), 조달 문서(구매 요청서·발주서), 회의록 작성 및 안건 관리를 지원합니다.