skill-writing-plans

To create a zero-context implementation plan, you generate a structured plan with explicit task scaffolding, ensuring each task is 2-5 minutes and includes file paths, code templates, tests, and verification steps before coding begins.

Zero-context guidance in software engineering planning provides complete upfront task scaffolding with mandated structures like YAML frontmatter, file paths, and verification steps, ensuring engineers need no additional context to execute implementation.

You break down engineering tasks by applying a reusable template that decomposes multi-step features into 2-5 minute increments, with each increment specifying file paths, code templates, tests, and verification steps for TDD workflows.

Yes, this implementation planning approach enforces validation gates and pre-execution contracts through strict plan structures and mandatory YAML frontmatter in SKILL.md files, ensuring plan completeness before any coding begins.

Yes, you can integrate these implementation plans with team workflows like CI checks and code reviews, using the enforced plan structure and validation gates to ensure completeness and scope alignment before implementation.

The mandated plan structure requires strict adherence to YAML frontmatter, explicit file paths, and verification steps for every 2-5 minute task, which may introduce overhead for simple or exploratory engineering tasks that do not require comprehensive upfront scaffolding.