Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/terrylica/cc-skills --skill go
The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Execute the ADR-driven 4-phase development workflow (preflight, implementation, formatting, release). Use whenever the user says 'itp go',
⛔ ITP Workflow — STOP AND READ
DO NOT ACT ON ASSUMPTIONS. Read this file first.
This is a structured workflow command. Follow the phases in order.
Your FIRST and ONLY action right now: Execute the TodoWrite below.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
⛔ MANDATORY FIRST ACTION: Plan-Aware Todo Integration
YOUR FIRST ACTION MUST BE a MERGED TodoWrite that preserves existing todos.
DO NOT:
❌ Overwrite existing todos from plan files or previous sessions
❌ Ignore the plan file at ~/.claude/plans/*.md
❌ Create your own todos without checking for existing ones
❌ Jump to coding without completing Step 0
❌ Create a branch before TodoWrite
Follow the full merge strategy (Steps 0.1-0.5) and TodoWrite template: Todo Merge Strategy
After TodoWrite completes, proceed to Preflight section below.
Quick Reference
Skills Invoked
Skill
Phase
Purpose
implement-plan-preflight
Preflight
ADR + Design Spec creation
adr-graph-easy-architect
Preflight
Architecture diagrams
impl-standards
Phase 1
Error handling, constants
mise-configuration
Phase 1
Env var centralization patterns
adr-code-traceability
Phase 1
Code-to-ADR references
code-hardcode-audit
Phase 1
Pre-release validation
semantic-release
Phase 3
Version tagging + release
pypi-doppler
Phase 3
PyPI publishing (if applicable)
File Locations
Artifact
Path
Notes
ADR
/docs/adr/$ADR_ID.md
Permanent
Design Spec
/docs/design/$ADR_ID/spec.md
Permanent, SSoT after Preflight
Global Plan
~/.claude/plans/<adj-verb-noun>.md
EPHEMERAL - replaced on new plan
Spec YAML Frontmatter
---adr:YYYY-MM-DD-slug# Links to ADR (programmatic)source:~/.claude/plans/<adj-verb-noun>.md# Global plan (EPHEMERAL)implementation-status:in_progress# in_progress | blocked | completed | abandonedphase:preflight# preflight | phase-1 | phase-2 | phase-3last-updated:YYYY-MM-DD---
Note: The source field preserves the global plan filename for traceability, but the file may no longer exist after a new plan is created.
Conventional commits -> tag -> release -> changelog -> push
3.3 PyPI Publishing (if -p flag)
Condition: Only execute if -p or --publish flag was provided.
Only if package pre-exists on PyPI:
MANDATORY Skill tool call: pypi-doppler -- activate NOW to publish
3.4 Earthly Pipeline
Use Earthly as canonical pipeline: non-blocking, observability-first, ensure GitHub Release exists, record stats/errors, Pushover alert, wire into GitHub Actions.
Phase 3 Success Criteria
ADR status updated to accepted or implemented
Release completed via semantic-release
If feature branch: PR created, Phase 3 skipped
Troubleshooting
Issue
Cause
Solution
TodoWrite not found
Skipped mandatory first step
Start from top of file, execute TodoWrite
ADR file not created
Preflight incomplete
Run Skill(itp:implement-plan-preflight)
Branch mismatch
Working on wrong branch
Switch to correct branch with git checkout
Phase 3 skipped
Not on main/master
Merge to main first, then run /itp:go -r
semantic-release fails
No GITHUB_TOKEN
Check token with echo $GITHUB_TOKEN
Diagram missing
graph-easy not invoked
Run Skill(itp:adr-graph-easy-architect)
Spec validation fails
Missing frontmatter fields
Check required fields in Quick Reference
Post-Execution Reflection
After this skill completes, reflect before closing the task:
Locate yourself. — Find this SKILL.md's canonical path (Glob for this skill's name) before editing. All corrections target THIS file and its sibling references/ — never other documentation.
What failed? — Fix the instruction that caused it. If it could recur, add it as an anti-pattern.
What worked better than expected? — Promote it to recommended practice. Document why.
What drifted? — Any script, reference, or external dependency that no longer matches reality gets fixed now.
Log it. — Every change gets an evolution-log entry with trigger, fix, and evidence.
Do NOT defer. The next invocation inherits whatever you leave behind.