notion-spec-to-implementation — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited notion-spec-to-implementation (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Transforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.
When asked to implement a specification:
Notion:notion-search to locate specification pageNotion:notion-fetch to read specification contentNotion:notion-create-pages for implementation planNotion:notion-search to locate tasks databaseNotion:notion-create-pages for individual tasks in task databaseNotion:notion-update-page to log progress and update status1. 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"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 blockersSee reference/spec-parsing.md for parsing patterns.
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))Use Notion:notion-create-pages:
- Title: "Implementation Plan: [Feature Name]"
- Content: Structured plan with phases, tasks, timeline
- Link back to original spec
- Add to appropriate location (project page, database)1. Search for task database:
- Use Notion:notion-search to find "Tasks" or "Task Management" database
- Look for engineering/project task tracking system
- If not found or ambiguous, ask user for database location
2. Fetch database schema:
- Use Notion:notion-fetch with database URL/ID
- Get property names, types, and options
- Identify correct data source from <data-source> tags
- Note required properties for new tasksFor each task in plan:
1. Create task in task database using Notion:notion-create-pages
2. Use parent: { data_source_id: 'collection://...' }
3. Set properties from schema:
- Name/Title: Task description
- Status: To Do
- Priority: Based on criticality
- Related Tasks: Link to spec and plan
4. Add implementation details in contentSee reference/task-creation.md for task patterns.
1. Update task status to "In Progress"
2. Add initial progress note
3. Document approach and decisions
4. Link relevant resourcesRegular updates:
1. Update task properties (status, progress)
2. Add progress notes with:
- What's completed
- Current focus
- Blockers/issues
3. Update implementation plan with milestone completion
4. Link to related work (PRs, designs, etc.)See reference/progress-tracking.md for tracking patterns.
Functional Requirements: User stories, feature descriptions, workflows, data requirements, integration points
Non-Functional Requirements: Performance targets, security requirements, scalability needs, availability, compliance
Acceptance Criteria: Testable conditions, user validation points, performance benchmarks, completion definitions
See reference/spec-parsing.md for detailed parsing techniques.
Plan includes: Overview → Linked Spec → Requirements Summary → Technical Approach → Implementation Phases (Goal, Tasks checklist, Estimated effort) → Dependencies → Risks & Mitigation → Timeline → Success Criteria
See reference/standard-implementation-plan.md for full plan template.
By Component: Database, API endpoints, frontend components, integration, testing By Feature Slice: Vertical slices (auth flow, data entry, report generation) By Priority:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.