Systemify
Drop these 3 files into any project and Claude Code will explore options, write detailed plans, and execute with validation.
> /explore adding a health check endpoint
Claude > I found 3 approaches. Here's my recommendation...
> /create-plan plans/pending/2026-01-15-health-check.md
Claude > Plan created with 4 steps and validation checklist.
> /implement plans/pending/2026-01-15-health-check.md
Claude > Implementation complete. All checks passed. Archived.
Works with Claude Code on Mac, Windows, and Linux
What's in the kit
Researches APIs, tools, and approaches before you commit to anything. Evaluates options with pros and cons, then writes a scoped recommendation.
Creates a detailed plan with step-by-step tasks, design decisions, validation checklist, and success criteria. Starts with a scope challenge so you don't overbuild.
Reads the plan, executes each step in order, runs the validation checklist, documents the work, and archives the completed plan.
The exact markdown format used across 40+ real projects. Status tracking, design decisions, validation checklists, and implementation notes.
A real plan that went from Draft to Implemented. See exactly what the output looks like at every stage of the workflow.
A Claude Code skill file so the workflow is always available. Claude understands the system and can guide you through it.
How it works
These are just markdown files that structure how Claude Code approaches your requests. Copy them in, start using the commands.
Copy the .claude/commands/ folder into your project. Create plans/pending/ and plans/completed/ directories.
Give Claude a vague idea. It researches your codebase, checks external APIs, and writes a scoped exploration document.
Claude expands the exploration into a step-by-step plan with validation criteria. Review it before any code gets written.
Claude executes the plan, validates each step, and archives the completed work. You get working code and a decision log.
The output
Instead of Claude diving into code and hoping for the best, you get a structured document that tracks decisions, validates results, and becomes a reference for future work.
What approaches exist, what they require, and which one makes sense for your project
Specific tasks, files affected, design decisions with rationale, and a validation checklist
What was built, any deviations from the plan, and issues encountered along the way
One markdown file per initiative. It starts as an exploration, becomes a plan, gets implemented, and moves to your completed archive. No separate trackers, no scattered notes.
From Daniel Canosa
Cold email pipelines, dashboard redesigns, API integrations, content systems. Every one went through explore, plan, implement. The completed plans folder is a searchable knowledge base of every decision I've made.
projects planned
businesses helped
YouTube subscribers
Free. No spam. Unsubscribe anytime.
© 2026 Systemify · Privacy