idea2product-p0-retire
Retire or abandon the current idea-to-product project only after showing the current handoff, collecting explicit confirmation, and recording a non-empty…
Skill by yichi2077
Chalk Labs
Need help deploying idea2product-p0-retire?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/yichi2077-idea2product-p0-retire
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/idea2product-p0-retire
What's inside
- Skill name
idea2product-p0-retire- Description
- Retire or abandon the current idea-to-product project only after showing the current handoff, collecting explicit confirmation, and recording a non-empty reason.
- License
- MIT
- Instructions
- 77 lines in SKILL.md · view on GitHub
Files (2)
- SKILL.md
- openai.yaml · agents/
SKILL.md (first lines)
# idea2product-P0-retire Use this when the user wants to abandon, terminate, archive, or retire the current idea-to-product project. Retire marks unfinished phases as `retired`; it does not delete files, erase completed work, or skip a phase inside an active project. Retirement is a state-changing operation. Never run it on a guess. ## Precheck 1. Walk upward from the current directory until `.pipeline/scripts/pipeline.py` exists. 2. If it does not exist, this workspace has no pipeline yet — tell the user to run `$idea2product-p0-guided-flow` to initialize it, then stop. Do not scaffold from this skill. 3. Run the read-only handoff brief first (use `python` on Windows): ```bash python3 .pipeline/scripts/pipeline.py handoff ``` Summarize the current phase, completed phases, gates, and next action before asking for confirmation. ## Mandatory dialogue — do NOT skip Before running retire, ask the user and WAIT for both: 1. **Explicit confirmation** — the user must clearly say they want to retire this project. 2. **Reason** — the concrete reason for abandoning or archiving this pipeline. Hard rules: - If confirmation is missing, stop and ask for it. - If the reason is missing or vague, ask again. Do not invent the reason. - If the user is trying to redo earlier work, use `$idea2product-p0-rollback` instead. - If the user only wants to check whether retirement is appropriate, run no state-changing command; explain the current status and options. Then confirm back and wait for an explicit "yes": > I'll retire this pipeline: unfinished phases will be marked `retired`, existing files > stay in place, and future work requires reopening a completed phase if you want to > resume. Reason: `<reason>`. Proceed? ## Execute Only after explicit confirmation and a non-empty reason, run (use `python` on Windows): ```bash python3 .pipeline/scripts/pipeline.py retire --reason "<reason from the user>" ``` If the engine rejects the request, relay the exact reason and stop. Never hand-edit state files. ## Broadcast result After a successful retire, run: ```bash python3 .pipeline/scripts/pipeline.py status ``` Summarize: - Which phases are now complete and which were marked retired. - That files were not deleted. - That the reason was recorded in `.pipeline/state/decision-log.md`. - That resuming meaningful work requires `$idea2product-p0-rollback` / `reopen <completed phase>`. ## Never - Never run `retire` without explicit confirmation and a user-provided reason. - Never use retire to skip a blocked gate or bypass phase work. - Never approve gates, edit state directly, or delete project files.
From yichi2077/idea2product-agent-kit, MIT.
Signals
- Stars
- 3
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Jun 14, 2026 (5 months ago)
- Last release
- Jun 16, 2026 (5 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get idea2product-p0-retire running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
idea2product-p0-retire skill. Agent Mart. https://agentmart.dev/skills/yichi2077-idea2product-p0-retire (last updated 2026-10-24)