What problem does it solve?
Notion boards often fail to interoperate with automation because property names, data_source_ids, and select/status options are assumed rather than verified, and tasks are created without a consistent structure or clear definition of done. This Skill eliminates guesswork by enforcing schema verification, consistent task pages, and correct status updates so boards remain reliable and predictable.
Core Features & Use Cases
- Schema-first validation: Always fetch the board schema to obtain exact data_source_id, case-sensitive property names, and available SELECT/STATUS options.
- Consistent task creation: Create pages with required properties (Title, Status), pass icon at creation, and include structured content sections: Goal, Steps, and Definition of Done.
- Status management and board reads: Update Status via notion-update-page, fetch individual pages to read Status, and present board state grouped by Not started / In progress / Done.
- Use case: Plan a sprint by fetching the board schema, adding backlog items with full Goal/Steps/DoD content, and moving tasks through Not started → In progress → Done.
Quick Start
Create a new Notion task titled Fix login bug with Status Not started including sections Goal, Steps, and Definition of Done after fetching the board schema.