# AI use cases for Forward Implementation First (Vuk97/forward-implementation-first) Repo: [Vuk97/forward-implementation-first](https://github.com/Vuk97/forward-implementation-first) | Use cases: 4 | Page: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/ A Markdown agent skill, installed with a shell script, that makes coding agents ship real work first and skip self-invented bookkeeping like hashes, locks, and receipts. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Unblock a pipeline stage stalled by a stale marker: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/unblock-stalled-pipeline-stage/ - Keep an agent building features over multi-day roadmaps: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/keep-agent-shipping-features/ - Coordinate parallel agents with one writer for publication: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/coordinate-parallel-agents-one-writer/ - Install the skill for Claude Code and Codex: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/install-skill-for-coding-agents/ ## How to unblock a pipeline stage stalled by a stale marker with Forward Implementation First Repo: [Vuk97/forward-implementation-first](https://github.com/Vuk97/forward-implementation-first) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run a blocked stage by hand, validate it, publish it, and continue from the cursor. **Who it is for:** A data or pipeline engineer whose staged run stopped because a hash or receipt no longer matches after one producer changed. **The problem:** The agent invalidates many completed stages over metadata drift and refuses to run the blocked stage manually, so no output ships. **The outcome:** The blocked stage runs, its output is validated and published, the cursor moves forward, and only the smallest affected cone is replayed. ### Steps 1. `git clone https://github.com/Vuk97/forward-implementation-first` 2. `cd forward-implementation-first` 3. `./install.sh` 4. Restart the agent so it loads the skill, since running sessions do not reload skills. 5. Ask the agent to classify the blocked action as semantic implementation, focused validation, or administrative bookkeeping, and to run the stage manually if only a marker blocks it. ### Prompt to paste into your agent ```text Using the forward-implementation-first skill in , run the stage blocked only by a stale receipt for manually, validate its output against its consumer, and publish it. Report the stage output path and the cursor position after the run. Verify that no stages outside the smallest affected dependency cone were invalidated. ``` ### Caveat The README describes the behavior as a suggestion the model decides to load, so an always-on rule or hook may be needed for the decision to hold every time. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/unblock-stalled-pipeline-stage/ ## How to keep an agent building features over multi-day roadmaps with Forward Implementation First Repo: [Vuk97/forward-implementation-first](https://github.com/Vuk97/forward-implementation-first) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Stop an agent from curating receipts and progress metadata instead of building. **Who it is for:** A developer who hands a roadmap to a coding agent that runs for days with little supervision. **The problem:** The agent spends hours regenerating markers and reports progress as receipts repaired, while the product output does not change. **The outcome:** The agent focuses on semantic implementation and focused validation, and bookkeeping is done only when the user asks or the artifact is part of the product. ### Steps 1. `git clone https://github.com/Vuk97/forward-implementation-first` 2. `cd forward-implementation-first` 3. `./install.sh` 4. Choose the project-scoped install by copying the skill directory to .claude/skills/ or .agents/skills/ in the repo, if you do not want it global. 5. Give the agent the roadmap and ask it to report the implementation and validation evidence for each item. ### Prompt to paste into your agent ```text Using the forward-implementation-first skill, work through the roadmap in in the repository, building features and running focused validation without generating hashes, locks, or certification markers. Report each completed item with its validation result. Verify that every reported result comes from a test, benchmark, or end-to-end run rather than a receipt. ``` ### Caveat The skill does not replace your own verification, and its claims about faster progress come from the author's experience, not from measured results in the README. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/keep-agent-shipping-features/ ## How to coordinate parallel agents with one writer for publication with Forward Implementation First Repo: [Vuk97/forward-implementation-first](https://github.com/Vuk97/forward-implementation-first) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Let workers prepare and inspect while one writer owns publication and cursor movement. **Who it is for:** A team lead running several agents or sessions against one repository at the same time. **The problem:** Multiple agents touch the same repository and risk becoming competing sources of truth, with unverified worker output merged into the main line. **The outcome:** Exactly one writer publishes and moves the cursor, workers' output is verified before use, and the team avoids invented busywork. ### Steps 1. `git clone https://github.com/Vuk97/forward-implementation-first` 2. `cd forward-implementation-first` 3. `./install.sh` 4. Designate one agent or session as the writer that owns publication, cursor movement, and conclusions. 5. Copy examples/execution-profile.md into your repo as a starting point for scheduling policy, and edit it to match your runtime, since the skill does not own scheduling. (inferred, check the README) ### Prompt to paste into your agent ```text Using the forward-implementation-first skill in , assign one agent as the single writer for publication and cursor movement, and have the other workers prepare and inspect . Report the worker outputs that were verified before consumption and the final publication. Verify that no worker output was merged without a check. ``` ### Caveat The README states that scheduling, worker counts, and wave sizes belong to your runtime, so the skill will not manage the parallelism itself. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/coordinate-parallel-agents-one-writer/ ## How to install the skill for Claude Code and Codex with Forward Implementation First Repo: [Vuk97/forward-implementation-first](https://github.com/Vuk97/forward-implementation-first) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Clone the repo and run the install script to add the skill to both agents. **Who it is for:** A developer who wants a default guardrail against bookkeeping stalls in Claude Code and Codex. **The problem:** Without the skill, each session needs the same decision rule pasted in by hand, and forgetting it costs days. **The outcome:** The skill is copied into the skill directories for Claude Code and Codex and loads by default in new sessions. ### Steps 1. `git clone https://github.com/Vuk97/forward-implementation-first` 2. `cd forward-implementation-first` 3. `./install.sh` 4. Check that the skill appears at ~/.claude/skills/forward-implementation-first/ and ~/.codex/skills/forward-implementation-first/. 5. Restart Claude Code and Codex so the new skill is loaded. ### Prompt to paste into your agent ```text Using the forward-implementation-first repository, install the skill for Claude Code and Codex on this machine. Report which skill directories now contain SKILL.md. Verify that both ~/.claude/skills/forward-implementation-first/ and ~/.codex/skills/forward-implementation-first/ exist after the install. ``` ### Caveat The README says running sessions do not reload skills, so the agent must be restarted before the install takes effect. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vuk97-forward-implementation-first/install-skill-for-coding-agents/