Can this skill modify my existing source code directly?

No. To maintain safety and architectural integrity, the skill is restricted to making modifications within the .collab/ directory during the rough-draft phase.

Why does the skill suggest context compaction?

Compaction checkpoints occur between phases to ensure Claude's context window remains efficient and focused as the design details become more granular.

What are the four phases of the Rough-Draft skill?

The skill progresses through Interface (defining contracts), Pseudocode (defining logic), Skeleton (mapping file structures), and Implementation Handoff (preparing for execution).

How does drift detection work?

After each phase, the skill compares the newly created artifacts against the original design document to identify changes, presenting them to the user for approval or rejection.

Do I need a collaboration session to use this skill?

Yes, an active collaboration session (initialized via /collab) is required to provide the necessary environment and state tracking for the rough-draft workflow.

Rough-Draft Design Bridge

Name: Rough-Draft Design Bridge
Author: ben-mad-jlp

byben-mad-jlp

Productivity & Workflow

Bridges the gap between brainstorming and implementation through a structured four-phase architectural refinement process.

About

The rough-draft skill acts as a rigorous architectural bridge that transforms high-level brainstorming concepts into concrete, implementation-ready specifications. By enforcing a disciplined four-stage progression—Interface, Pseudocode, Skeleton, and Implementation Handoff—it ensures that architectural integrity is maintained and logic is fully vetted before production code is written. The skill features automated drift detection to catch deviations from the original design doc and utilizes MCP-powered collaboration tools to manage artifacts safely within a dedicated environment, preventing premature modifications to source files.

Key Features

Context Compaction Checkpoints to optimize token usage between phases
Automated Drift Detection with pro/con analysis for design changes
Structured Verification Gates to ensure alignment before phase transitions
4-Phase Progressive Refinement (Interface, Pseudocode, Skeleton, Handoff)
0 GitHub stars
Integrated MCP Collaboration for real-time document and diagram updates

Use Cases

Validating intricate business logic via pseudocode before initiating TDD
Transitioning complex brainstorming sessions into actionable technical specifications
Enforcing architectural standards and interface contracts in collaborative environments

About

Key Features

Context Compaction Checkpoints to optimize token usage between phases
Automated Drift Detection with pro/con analysis for design changes
Structured Verification Gates to ensure alignment before phase transitions
4-Phase Progressive Refinement (Interface, Pseudocode, Skeleton, Handoff)
0 GitHub stars
Integrated MCP Collaboration for real-time document and diagram updates

Use Cases

Validating intricate business logic via pseudocode before initiating TDD
Transitioning complex brainstorming sessions into actionable technical specifications
Enforcing architectural standards and interface contracts in collaborative environments