Skills notion-spec-to-implementation
📦
notion-spec-to-implementation
Content revision r2 Safe ⚙️ External commands🌐 Network access
Convert Notion Specs Into Implementation Plans
Feature specifications often lack an actionable delivery structure. This skill converts Notion specs into linked plans, tasks, and progress updates.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "notion-spec-to-implementation" from https://skillstore.io/skills/davila7-notion-spec-to-implementation.md and its manifest at https://skillstore.io/api/skills/davila7-notion-spec-to-implementation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "notion-spec-to-implementation". Create a quick implementation plan for the Notion spec named Audit Log Export.
Expected outcome:
- Overview: Deliver CSV export for filtered audit logs.
- Requirements: Preserve active filters, stream large exports, and record export events.
- Phases: Confirm schema, implement export service, add interface controls, test limits, and release.
- Linked tasks: Define export contract; build streaming endpoint; add export action; test permissions and large datasets.
Using "notion-spec-to-implementation". Break the Customer Merge specification into tasks and identify unresolved decisions.
Expected outcome:
- Clarifications: Define the surviving customer rule and confirm merge permissions.
- Tasks: Validate candidates; design conflict handling; implement merge transaction; add audit history; test rollback and authorization.
- Dependencies: Customer data schema, identity service, and compliance review.
- Success criteria: Authorized users merge eligible records without data loss and can review a complete audit trail.
Using "notion-spec-to-implementation". Prepare a progress update for phase two of the billing migration.
Expected outcome:
- Status: Phase two is in progress with three of five tasks complete.
- Completed: Historical invoice mapping, reconciliation queries, and staging validation.
- Blocker: Finance approval is required for rounding behavior.
- Next steps: Resolve rounding rules, complete production rehearsal, and publish the milestone summary.
Security Audit
Safev9 • 7/23/2026 Open versioned report
All static findings are false positives caused by Markdown inline-code formatting, standard Codex setup commands, or an ordinary section heading. The skill contains no executable scripts, shell interpolation, suspicious endpoint, prompt injection, or network reconnaissance behavior.
1
Files scanned
59
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (21)
🌐 Network access (1)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-notion-spec-to-implementation/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-notion-spec-to-implementation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-notion-spec-to-implementation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-notion-spec-to-implementation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-notion-spec-to-implementation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). notion-spec-to-implementation security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-notion-spec-to-implementation/audits/9BibTeX citation
@techreport{davila7-davila7-notion-spec-to-implementation-2026,
author = {davila7},
title = {notion-spec-to-implementation security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-notion-spec-to-implementation/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "notion-spec-to-implementation security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/davila7-notion-spec-to-implementation/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-notion-spec-to-implementation:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance
What You Can Build
Structure a feature delivery plan
Convert a product requirement into linked phases, dependencies, risks, and success criteria.
Create engineering tasks
Break a reviewed specification into scoped tasks with acceptance criteria and database properties.
Maintain implementation status
Keep the plan, tasks, blockers, decisions, and milestone summaries aligned during delivery.
Try These Prompts
Review a specification
Find the Notion page titled [SPEC TITLE]. List its requirements, acceptance criteria, constraints, priorities, ambiguities, and assumptions. Do not create pages yet.
Create a quick plan
Convert [SPEC TITLE] into a quick implementation plan. Link the plan to the spec and include phases, dependencies, risks, and success criteria.
Build a task breakdown
Create implementation tasks from [SPEC TITLE] in [TASK DATABASE]. Confirm required properties first. Scope each task for one or two days.
Coordinate a phased delivery
Create a standard plan for [SPEC TITLE], generate linked tasks in [TASK DATABASE], and record dependencies, blockers, decisions, progress updates, and milestone summaries.
Best Practices
- Resolve ambiguous Notion search results and specification gaps before creating plans or tasks.
- Confirm database properties and data source identifiers before writing task pages.
- Keep relations, status fields, blockers, decisions, and milestone summaries synchronized.
Avoid
- Do not create tasks from an incomplete specification without recording assumptions and clarifications.
- Do not write pages into an unconfirmed database or guess required property values.
- Do not assign dates, owners, priorities, or estimates that the specification does not provide.
Frequently Asked Questions
Does this skill require Notion access?
Yes. It requires a configured Notion MCP connection and OAuth access to the relevant workspace.
Can it choose between several matching specifications?
It searches first and asks the user to select a page when results are ambiguous.
What plan formats does it support?
It distinguishes quick plans for simple changes from standard plans for multi-phase features and migrations.
Can it create tasks in an existing database?
Yes. It confirms the database schema and required properties before creating linked task pages.
Does it implement the feature?
No. It produces and maintains planning artifacts but does not write or test application code.
Are all referenced templates included?
No. The audited package contains only SKILL.md, while the instructions reference separate template and example files.