跳到正文
cccskills
免费在 GitHub 公开

fp-implement

Implement 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.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

ci-churn

免费

Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月20日 更新

Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月20日 更新

One-fix-at-a-time, approval-gated design fix recovery. Given a checklist of fixes (handover doc, CHECKLIST.md, or inline list), applies each individually, presents a diff, and waits for an explicit APPROVE / REJECT / NO CHANGES decision before committing. Trigger phrases: /design-iteration, "go through the checklist one by one", "fix these one at a time", "bucket recovery", "design fix pass".

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月20日 更新

Playbook for correcting a named skill's star level to match its computed Trust Magnitude grade, with an independent post-calibration verification pass and a CLI-logged timeline event (never hand-written). Use when: recalibrating a skill's level, fixing a stale or drifted star rating, running a batch of `gaia dev calibrate` corrections, or confirming a past calibration actually landed. Triggers: "calibrate <skill>", "recalibrate the trust magnitude backlog", "promote/demote <skill> to N stars", "why is <skill> still N stars", "verify a calibration actually landed", "Hall of Heroes ranking is wrong".

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月20日 更新

Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月20日 更新

Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月20日 更新

查看 gaia-research 的全部技能

报告此技能的问题