writing-workbench/docs/superpowers/plans/2026-06-15-rebuild-writing-...

2.9 KiB

Rebuild Writing Workbench Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Rebuild Writing Workbench as a local tool-calling and process-record workspace that starts from a Web-generated initial outline.

Architecture: Preserve the existing Git repository identity and replace the old article-production-runtime scaffold with a smaller documentation and template system. Projects live directly under projects/; supplier needs are recorded under requirements/ccpe/ or requirements/skills-vault/.

Tech Stack: Markdown documentation, Git, Windows PowerShell for filesystem operations.


Task 1: Clear Old Workspace

Files:

  • Delete old workspace files and folders except .git.

  • Step 1: Verify workspace path

Run: Resolve-Path .

Expected: C:\Users\wangq\Documents\Codex\writing-workbench

  • Step 2: Remove old files

Run a guarded PowerShell removal that refuses to operate outside the expected workspace.

Expected: only .git remains.

Task 2: Create New Skeleton

Files:

  • Create: docs/

  • Create: projects/

  • Create: requirements/ccpe/

  • Create: requirements/skills-vault/

  • Create: templates/article-project/

  • Create: templates/requirements/

  • Step 1: Create folders

Run: New-Item -ItemType Directory -Force for each target directory.

Expected: all target directories exist.

Task 3: Write New Operating Documents

Files:

  • Create: README.md

  • Create: WORKBENCH.md

  • Create: docs/operating-playbook.md

  • Create: docs/project-lifecycle.md

  • Create: docs/invocation-policy.md

  • Create: docs/capability-requests.md

  • Step 1: Write documents

Expected: documents define Web initial outline entry, user-directed advancement, real invocation policy, and capability-request pause behavior.

Task 4: Write Templates

Files:

  • Create: templates/article-project/PROJECT_STRUCTURE.md

  • Create: templates/article-project/project.md

  • Create: templates/article-project/source-map.md

  • Create: templates/article-project/status.md

  • Create: templates/article-project/decision-log.md

  • Create: templates/requirements/ccpe-request.md

  • Create: templates/requirements/skills-vault-request.md

  • Step 1: Write project and supplier templates

Expected: templates match the new workflow and do not include old active/completed/runtime assumptions.

Task 5: Verify

Files:

  • Inspect all created Markdown files.

  • Inspect Git status.

  • Step 1: List files

Run: Get-ChildItem -Recurse -File

Expected: only rebuilt files are present outside .git.

  • Step 2: Check Git status

Run: git status --short

Expected: old tracked files are deleted and new rebuilt files are untracked or modified.