Why are placeholders like '// ...' forbidden?

To prevent ambiguity and logic gaps; the skill requires complete code to ensure the execution phase is seamless and error-free for the executor agent.

What makes this skill different from regular AI planning?

Unlike standard AI suggestions, this skill forbids vague language and requires full code blocks, ensuring plans are immediately executable by subagents or developers without further clarification.

Where are the plans saved?

Plans are formatted to be saved in a project's 'docs/plans/' directory using a standardized date-based naming convention for easy tracking.

Can I use this for existing projects?

Yes, it is designed to integrate with existing systems by requiring architectural context and exact file paths within your current repository structure.

Does it support Test-Driven Development (TDD)?

Absolutely. The skill mandates writing failing tests and showing expected terminal output before providing the actual implementation code.

Precision Implementation Planning

Name: Precision Implementation Planning
Author: BaxterCooper

byBaxterCooper

Productivity & Workflow

Generates rigorous, execution-ready implementation plans featuring complete code blocks and exact file paths for autonomous agents.

About

The Writing Plans skill enforces a strict, code-first approach to project planning, eliminating ambiguity for both human developers and AI subagents. By mandating exact file paths, full implementation code (not snippets), and expected test outputs, it creates a foolproof roadmap for the Nexus orchestration engine. This skill is essential for maintaining high standards in Test-Driven Development (TDD) and ensuring that complex feature migrations or additions are documented with 100% technical accuracy before a single line of production code is changed.

Key Features

Integrated verification steps with expected failure and success outputs
Strict prohibition of vague language and placeholders like '// ...'
0 GitHub stars
Automated file path tracking for new and modified components
Standardized Markdown plan headers with architecture and stack details
Requirement for complete, copy-pasteable code blocks for every task

Use Cases

Designing complex features that require multi-file orchestration by AI subagents
Creating standardized implementation logs for team-wide consistency in project documentation
Documenting technical roadmaps for TDD workflows where tests must fail before implementation

About

Key Features

Integrated verification steps with expected failure and success outputs
Strict prohibition of vague language and placeholders like '// ...'
0 GitHub stars
Automated file path tracking for new and modified components
Standardized Markdown plan headers with architecture and stack details
Requirement for complete, copy-pasteable code blocks for every task

Use Cases

Designing complex features that require multi-file orchestration by AI subagents
Creating standardized implementation logs for team-wide consistency in project documentation
Documenting technical roadmaps for TDD workflows where tests must fail before implementation