AIPM: Project Management with AI-Powered Automation

Introduction

AIPM (AI‑powered Project Management) v0 is an innovative framework designed by Miyatti that uses PMBOK, Lean UX, and Agile methodologies—streamlines the project lifecycle through AI assistance and structured documentation workflows.

Core Components

  1. Three-tier document structure:
    Flow: a draft workspace with date‑organized notes.
    Stock: approved, formal deliverables stored by phase.
    Archive: immutable records of completed projects.
  2. Workflow engine: LLM-assisted “Ask → Draft → Review → Sync” process, managed by a robust rules engine built on .mdc files.
  3.  Hybrid methodology:
    PMBOK for structure (“What”).
    Lean UX for discovery (“Why”).
    Agile for execution (“How”).

Strengths

  • Efficient documentation: Only drafts that pass review move to Stock, reducing clutter and focusing on essential deliverables.
  • Methodological rigor: Combines PMBOK’s structure, Lean UX’s problem framing, and Agile’s adaptability in a unified workflow.
  • LLM-powered automation: Accelerates document creation with tailored prompts and templates, reducing repetitive admin tasks.
  • Customizable rules: Built around easy-to-edit .mdc files (e.g., 00_master_rules, flow_to_stock_rules), making it extensible and flexible.
  • Seamless dev integration: Includes support for development workflows (e.g., environment setup, story planning), ensuring tech tasks are synced with PM processes.

Weaknesses

  • Steep learning curve: Requires familiarity with .mdc syntax and rule logic to fully harness system capabilities.
  • Tool & language lock-in: Depends on the Cursor editor and Japanese trigger phrases.
  • Version Control Complexity: Managing collaborative work across the Flow/Stock/Archived structure may become complex in larger teams without proper version control strategies.

How to use

A. System Requirements

  • Cursor editor for LLM prompts.
  • Git for cloning the repo.
  • Bash or compatible shell.

B. Quick Setup (via Cursor)

  • Open Cursor and select New Window.
  • Enter the repository URL: https://github.com/miyatti777/aipm_v0.
  • In the Chat panel, type: “Please perform initial setup / 初期設定お願いします” — Cursor will automate folder structure and rule setup.

C. Manual Setup

  • Clone the Repository.
    git clone https://github.com/miyatti777/aipm_v0.git
    cd aipm_v0
  • Run Setup Script.
    ./setup_workspace_simple.sh setup_config.sh
  • Verify the directory structure.

D. Configuration Options

  • Edit setup_config.sh (AUTO_APPROVE, AUTO_CLONE, RULE_REPOS, PROGRAM_REPOS) to customize behaviors, templates.
  • Set user rules from the Cursor settings (you can change the original rules from Japanese to English).
    #========================================================
    # 0. Base Policy
    #========================================================
    ! Always respond in English
    – Check if any rules are attached. If so, be sure to load them. Mark with ✅ once loaded.
    – Deliverables should be created as files using `edit_file` where possible (split into smaller parts).
    – Tasks such as MCP or file viewing should be executed autonomously if possible.
    – When receiving a task request, identify missing information, plan by yourself, and proceed to the goal.#========================================================
    # 0. Safe Execution of Shell Commands
    #========================================================
    ! Important: Prohibited and recommended practices when executing commands
    – Absolutely do not use subshell functions (`$(command)` format).
    – Backticks (“command“) are also prohibited.
    – Complex commands using pipes (`|`) or redirects (`>`) must be broken into simple, individual commands.
    – When date information is needed:
    1. First, run a standalone `date` command and get the terminal output.
    2. Use the resulting date string explicitly in the next command.
    3. Example: Run `date +%Y-%m-%d` → output `2024-05-12` → use this string directly.! Command Execution Example
    – Not Allowed: `mkdir -p Flow/$(date +%Y%m)/$(date +%Y-%m-%d)`
    – Allowed: [Break into the following two steps]
    1. `date +%Y%m`
    2. `date +%Y-%m-%d`
    3. `mkdir -p Flow/{output1}/{output2}`#========================================================
    # 1. Mandatory Rule File References (pre-load)
    #========================================================
    # * Prioritize loading `pmbok_paths_*.mdc` first. All subsequent paths
    # should be referenced using {{dirs.*}} / {{patterns.*}} variables.required_rule_files:
    – /Users/<YOUR_USER>/{{PROJECT_ROOT}}/.cursor/rules/basic/pmbok_paths.mdc
    – /Users/<YOUR_USER>/{{PROJECT_ROOT}}/.cursor/rules/basic/00_master_rules.mdc

E. Usage

Project Initialization

  • Start by typing: “I want to make curry. Please start a project.” (Japanese: カレー作りたい プロジェクト開始して).

  • After that, you can continue with commands like:
    “I want to create a project charter.”
    “Define the product.”
    “I want to do stakeholder analysis.”
  •  For each step, the AI will ask for your confirmation. If everything looks good, you can reply with “Confirm and reflect” to proceed.

You can continue with other phases, as shown in this example: [Usage by phase]

 

References

https://github.com/miyatti777/aipm_v0

https://deepwiki.com/miyatti777/aipm_v0

Sync Your Kindle Highlights to Obsidian

If you use Obsidian for note-taking and read books on Kindle, the Obsidian Kindle Highlights plugin is a game-changer. This plugin lets you import your Kindle highlights directly into your Obsidian vault.

Key Features

  • Sync highlights from your Kindle (via My Clippings.txt or Amazon account).

  • Customize note format with templates.

  • Make highlights searchable and linkable in Obsidian.

 

How to Use

  1. Install and enable the plugin from Obsidian’s community plugins.
  2. Upload your My Clippings.txt.
  3. Click ‘Sync Now’ to sync your highlights using the default format.
  4. Feel free to adjust the templates later to fit your needs.
  5. Take a look at my sample template below.
    File name

    {{author}}-{{title}}


    File content


    tags: kindle
    status: currently reading

    # {{longTitle}}
    ## Metadata
    {% trim %}
    {% if authorUrl %}
    * Author: [{{author}}]({{authorUrl}})
    {% elif author %}
    * Author: [[{{author}}]]
    {% endif %}
    {% endtrim %}

    ## Highlights
    {{highlights}}


    Highlight

    Highlight: {{text}}

    – Page: {{page}}

    {% if note %}
    – Note: {{note}}
    {% endif %}


 

 

Summary: The Obsidian Kindle Highlights plugin makes it easy to import and organize your Kindle highlights in Obsidian, helping you build a useful, searchable knowledge base from your reading.

 

 

Dify MCP Plugin & Zapier: A Hands-On Guide to Agent Tool Integration

Introduction

Leverage the power of the Model Context Protocol (MCP) in Dify to connect your agents with Zapier’s extensive application library and automate complex workflows. Before we dive into the integration steps, let’s quickly clarify the key players involved:

  • Dify: This is an LLMops platform designed to help you easily build, deploy, and manage AI-powered applications and agents. It supports various large language models and provides tools for creating complex AI workflows.
  • Zapier: Think of Zapier as a universal translator and automation engine for web applications. It connects thousands of different apps (like Gmail, Slack, Google Sheets, etc.) allowing you to create automated workflows between them without needing to write code.
  • MCP (Model Context Protocol): This is essentially a standardized ‘language’ or set of rules. It allows AI agents, like those built in Dify, to understand what external tools (like specific Zapier actions) do and how to use them correctly.

Now that we understand the components, let’s explore how to bring these powerful tools together.


Integrating Zapier with Dify via MCP

Zapier Setup

  1. Visit Zapier MCP Settings.
  2. Copy your unique MCP Server Endpoint link.
  3. Click “Edit MCP Actions” to add new tools and actions.
  4. Click “Add a new action”.
  5. Select and configure specific actions like “Gmail: Reply to Email”.
  6. To set up:
    – Click “Connect to a new Gmail account”, log in, and authorize your account.

    – For fields like thread, to, and body, select “Have AI guess a value for this field”.
  7. Repeat to expand your toolkit with “Gmail: Send Email” action.

MCP Plugins on Dify

  • MCP SSE: A plugin that communicates with one or more MCP Servers using HTTP + Server-Sent Events (SSE), enabling your Agent to discover and invoke external tools dynamically.
  • MCP Agent Strategy: This plugin integrates MCP directly into Workflow Agent nodes, empowering agents to autonomously decide and call external tools based on MCP-defined logic.

MCP SSE

Customize the JSON template below by inputting your Zapier MCP Server URL in place of the existing one. Paste the resulting complete JSON configuration into the installed plugin.

{
“server_name”: {
“url”: “https://actions.zapier.com/mcp/*******/sse”,
“headers”: {},
“timeout”: 5,
“sse_read_timeout”: 300
}
}

 

 

After setting things up, proceed to create a new Agent app. Ensure you enable your configured MCP SSE plugin under ‘Tools’. This allows the Agent to automatically trigger relevant tools based on the user’s intent, such as drafting and sending emails via an integrated Gmail action.

MCP Agent Strategy

Besides the SSE plugin, the MCP Agent Strategy plugin puts MCP right into your workflow’s Agent nodes. After installing it, set up the MCP Server URL just like before. This allows your workflow agents to automatically use Zapier MCP on their own to do tasks like sending Gmail emails within your automated workflows.


Final Notes

Currently (April 2025), Dify’s MCP capabilities are thanks to fantastic community plugins – our sincere thanks to the contributors! We’re also developing built-in MCP support to make setting up services like Zapier MCP and Composio within Dify even easier. This will unlock more powerful integrations for everyone. More updates are coming soon!

References: Dify MCP Plugin Hands-On Guide: Integrating Zapier for Effortless Agent Tool Calls

 

 

 

 

 

Posted in AI