plan-workspace

Manage a canonical plan document for initiatives with iterative updates and decision logging.

Updated Aug 27, 2026

Search Tags:#workflow #planning #documentation #decision logging #agent execution #initiative management

Ready to run

npx skills add https://github.com/helpful-bits/plantocode --skill plan-workspace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-workspace
Source: https://github.com/helpful-bits/plantocode/tree/main/.agents/skills/plan-workspace
Command: npx skills add https://github.com/helpful-bits/plantocode --skill plan-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the management of initiative plans by maintaining a single, canonical document, preventing fragmented notes and ensuring decisions are explicit.

Core Features & Use Cases

Centralized Planning: Consolidates all planning artifacts (context, objectives, constraints, architecture, rollout, questions, done criteria) into one document.
Iterative Updates: Ensures the same document is updated across iterations, providing a clear history of decisions and progress.
Use Case: When starting a new feature development, use this Skill to create and maintain the master plan document, tracking progress and decisions from inception to completion.

Quick Start

Use the plan-workspace skill to create a new plan document for the 'user authentication' initiative.

Frequently Asked Questions about plan-workspace

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

FAQPage Schema

How do I maintain a single canonical plan document for an ongoing initiative?▼

To maintain a canonical plan document, this Skill consolidates context, objectives, constraints, architecture, and rollout details into one file. It supports iterative updates so the same document evolves across iterations without fragmenting notes.

What is the best way to log decisions for agent-first workflows?▼

Logging decisions for agent-first workflows requires explicit tracking within a centralized plan. This Skill records decisions directly in the master planning document, ensuring agent execution follows a clear history of objectives, constraints, and completion criteria.

How do I track open questions and completion criteria during feature development?▼

Tracking open questions and completion criteria happens automatically by structuring them into the canonical plan document. This Skill ensures these artifacts remain visible and updated alongside architecture and rollout plans throughout the development lifecycle.

Can I support parallel subagent execution using a plan manifest?▼

Yes, parallel subagent execution is supported via codex exec with a manifest. This allows agent-first workflows to distribute initiative management tasks while updating the single canonical planning document.

Does initiative management work without prerequisite dependencies?▼

Yes, initiative management works without external dependencies. The Skill operates independently using internal scripts to manage planning artifacts, requiring only your initiative context to generate and maintain the master plan.