gaia-research/gaia-skill-tree / .agents/skills/fp-implement
fp-implement
VerifiedImplement a scoped feature-pipeline plan in coherent commits and push each meaningful unit. Use for "implement the plan", "apply the plan", or the implementation stage; routine lean/economy work does not require planApproved, while explicit human gates remain binding.
Implement the plan
Objective: leave a tested, inspectable change on the correct feature branch.
Shared execution contract
Read ../feature-pipeline/SKILL.md relative to this skill directory. Inherit its
mode, authority, hard stops and finish-state proof. Default is structured economy;
lean mode may combine stages. A routine checkpoint records progress and continues
in lean/economy mode. Only explicit hard-gated milestones or an actual unapproved
authority boundary wait for human approval. Standalone invocation ends when this
skill's scoped deliverable is complete; it does not require approval to perform
already-authorized work. Use the actual harness tools, never invented spawn APIs.
State helper: bash .agents/skills/feature-pipeline/scripts/state.sh.
Inspect existing state and Git/PR state before work. State and planApproved are
recovery notes, never authorization or L4 approval. Refer to the shared skill's
checkpoint command before advancing; do not classify a real boundary as routine.
Work and done-check
Read the current plan and finish-state checks; verify actual branch/worktree and recover existing commits. Phase 3 signals planning is complete. Missing or stale plan content requires recovery from live evidence, not blind guesses. Never checkout over unfinished changes or recreate completed work.
For hard-gated mode, require genuine operator approval for M2-plan before code.
For lean/economy mode, planApproved == false is not a blocker to ordinary bounded
work. In all modes stop before any actual unapproved authority boundary, even if
planApproved == true. Human L4 and CLI authorization are never inferred from it.
Implement coherent units, run appropriate tests, inspect output, repair failures, and stage only relevant files. Confirm branch immediately before each commit and push each meaningful commit immediately. No force-push or history rewrite. Keep commit boundaries reviewable; a plan bullet need not equal one commit.
Registry mutations use canonical CLI commands with authorization, L4, provenance,
evidence and schema checks intact. Never hand-edit registry or timeline data.
Regenerate required Class S artifacts with the canonical builder and include them
with the source change; leave Class P untracked. Do not repeat the old blanket ban
on committing required docs/graph/* outputs.
Diagnose import/test failures and fix within scope. Escalate with evidence when blocked outside authority or after three identical failures with no new diagnosis; ordinary obstacles do not mandate a user pause. Preserve interrupted work safely and report the exact incomplete state rather than claiming completion.
Done: scoped behavior and tests pass locally, actual output is inspected and
meaningful commits are pushed. Advance phase to 4, record evidence and continue to
fp-review in a full run. Hard-gated M2 waits with the diff and test receipt.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |