notion-task-patterns

Document Notion task templates for user stories, bugs, and improvements.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill notion-task-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notion-task-patterns
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/notion-task-patterns
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill notion-task-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This legacy skill captures Notion task patterns and templates to help teams maintain consistency in Notion-based task management during MCP workflows. It serves as a historical reference for how tasks were modeled and documented.

Core Features & Use Cases

  • Reference templates for common Notion task categories: Feature (User Story), Bug, Improvement/Refactor, Documentation, Prototyping, and Log.
  • Guidance on Notion database structure, required properties, and example blocks to illustrate how tasks should be documented.
  • Use Case: Teams migrating from Notion MCP tooling to Flyee API can consult these patterns to understand prior conventions and mappings.

Quick Start

Refer to the Notion task templates to replicate the recommended structure for User Stories, Bugs, Improvements, and Prototypes.

Frequently Asked Questions about notion-task-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are standard Notion task patterns for MCP workflows?

Standard Notion task patterns for MCP workflows include templates for User Stories, Bugs, Improvements, Documentation, Prototyping, and Logs, defining database naming conventions, mandatory properties, and sample payloads to standardize task creation.

How do I structure a Notion database for engineering task management?

Structure a Notion database for engineering tasks by applying mandatory properties and example blocks for categories like Features and Bugs. This skill provides reference templates that specify required fields and sample payloads for consistent task documentation.

What Notion task schemas should I reference during a Flyee API migration?

During a Flyee API migration, reference Notion task schemas for User Stories, Bugs, Improvements, and Prototypes. These historical patterns map prior database conventions and mandatory properties to help teams understand legacy task structures.

Do I need to execute code to use these Notion task templates?

No, you do not need to execute code to use these Notion task templates. This skill serves strictly as a static reference guide, providing documentation on database structure and sample payloads without running any code execution.

Why is this Notion task patterns reference considered deprecated?

This Notion task patterns reference is considered deprecated because it captures historical templates used before migrating to the Flyee API. It remains available for engineering teams to consult prior conventions and database mappings.

Can I use these Notion task patterns for documenting code refactoring?

Yes, you can use these Notion task patterns for documenting code refactoring. The skill includes specific Improvement and Refactor templates with required properties and example blocks to standardize how refactoring tasks are documented.