09-SKILL-WRITING-PLANS

You can generate a multi-step implementation plan by providing a spec or requirement, which produces a structured roadmap listing required files, execution steps, verifications, and testing criteria before development begins.

Documenting task plans for feature rollouts requires a standardized plan header and granular tasks that explicitly map touched files, validations, and testing criteria to ensure a clear, testable execution roadmap.

Implementation plan drafts are saved using a date-based naming convention under knowledge/playbooks/drafts, creating traceable markdown files formatted as YYYY-MM-DD-<feature-name>.md for easy retrieval.

Yes, implementation plans support multiple workflow types including INBOX processing plans, agent creation plans, and restructuring plans, covering end-to-end product development and complex initiatives.

An implementation plan for multi-step tasks should include a standardized plan header, granular execution steps, touched files, validation checks, and specific testing criteria to guide execution accurately.

You need to draft a comprehensive step-by-step plan before execution whenever handling complex initiatives, feature rollouts, or product development where explicit steps and testing criteria must be documented.