plan-close

Batch sync .spec/{slug}/ design docs to Notion and commit to Git.

9|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mark22013333/crew --skill plan-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-close
Source: https://github.com/mark22013333/crew/tree/main/plugins/feature-workflow/skills/plan-close
Command: npx skills add https://github.com/mark22013333/crew --skill plan-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates scattered design documents from the .spec/{slug}/ directories by batch syncing them to Notion, updating statuses, syncing to the knowledge base, and committing design files to Git, enabling a streamlined closure workflow.

Core Features & Use Cases

  • Batch-syncs all relevant design files from .spec/{slug}/ into Notion blocks, updates status, and pushes to the knowledge base.
  • Supports both Feature-type and Bug-type workflows, ensuring design docs are linked to project metadata and version control.
  • Example: When a feature or bug is ready to close, run plan-close to reflect the latest specs, update Notion, and commit the changes to Git.

Quick Start

Run /plan-close to batch-sync all .spec/{slug}/ design documents to Notion and finalize the closure by updating the knowledge base and pushing changes to Git.

Frequently Asked Questions about plan-close

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

FAQPage Schema
How do I batch-sync design docs from .spec directories to Notion?

To batch-sync design docs to Notion, you can use this Skill to automatically consolidate scattered files from .spec/{slug}/ directories into Notion blocks, update statuses, and sync to your knowledge base.

What's the best way to automate plan closure and sync design docs to Git?

Automating plan closure requires syncing design docs to Notion, updating project metadata, and committing final files to Git. This Skill handles that end-to-end workflow, ensuring version control and knowledge base entries stay traceable.

Do I need Notion IDs configured to sync .spec design documentation?

Yes, you need Notion IDs configured in config.md, a prod_branch defined in projects/{repo-id}.md, and Git access to commit final design files before running the batch-sync and closure process.

Can I use this plan closure workflow for both features and bugs?

Yes, this plan closure workflow supports both Feature-type and Bug-type workflows across repositories, ensuring design docs are linked to project metadata and version control for either scenario.

Why does syncing .spec design docs to Notion require Git access?

Syncing .spec docs to Notion requires Git access because the closure process finalizes by committing the final design files to a prod_branch, ensuring version control and project metadata stay in sync.

What happens to project metadata when closing a plan in Notion?

When closing a plan, project metadata is updated automatically alongside the batch sync of design docs to Notion, ensuring status updates and knowledge-base entries remain traceable across repositories.