[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C6QMSSWNKS33Z4N2Z91H04":3,"skill-same:01M7C6QMSSWNKS33Z4N2Z91H04":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7C6QMSSWNKS33Z4N2Z91H04","continue-implementation",null,"Use when the user asks Pi to continue implementation, continue-implementing, resume implementation, or run a HEPHA FEAT implementation such as \"use the skill continue implementation for FEAT-002\" from a registered project workspace.","aboimpinto\u002FAgenticDevelopmentProcess","aboimpinto","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1231687?v=4","01M7C6P0WDWM5B2RBSKSPR66PZ","Paulo Aboim Pinto","01M7C6P0WXGYZP7QMFS91N8C3P",0,"MIT","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fcontinue-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: continue-implementation\ndescription: Use when the user asks Pi to continue implementation, continue-implementing, resume implementation, or run a HEPHA FEAT implementation such as \"use the skill continue implementation for FEAT-002\" from a registered project workspace.\nagent_action: continue-implementing\n---\n\n# Continue Implementation\n\n## Model Authority\n\nThis procedure is model-neutral. When invoked directly, execution is\n`direct_host` and remains in the current Pi, Codex, or Claude Code session; that\nactive host owns model selection. Do not query Hepha routing policy, request a\nmodel switch, automatically hand off, choose a fallback model, or fabricate\nroute-policy evidence. Direct execution does not fabricate an orchestrated\nreceipt. Only an explicit Hepha launcher or dashboard dispatch creates a\nseparate `orchestrated` worker, whose route is injected outside this skill.\n\nYou are executing the HEPHA `continue-implementing` workflow directly from Pi.\n\nThis skill is for the direct Pi workflow, not for clicking the dashboard. It\nmust work when Pi is opened from a registered project or a parent workspace and\nthe user names the active project and a FEAT id such as `FEAT-002`.\n\n## Objective\n\nResolve the active HEPHA project and MemoryBank, locate the requested FEAT, read\nits `PhaseExecutionContract.json`, and continue the first unresolved declared\nphase autonomously in contract order until every declared phase is `COMPLETED`\nor `SKIPPED`, or until a real blocker requires human input.\n\n## Required Inputs\n\nAccept these from the user's message:\n\n- project name or alias, such as `HEPHA`, `Hepha`, or `AgenticDevelopmentProcess`;\n- FEAT id, such as `FEAT-002`;\n- optional MemoryBank path override;\n- optional mode, where `autonomous` means continue through subsequent phases\n  without stopping after one phase.\n\nIf the FEAT id is missing, ask one concise question. Otherwise, infer safely.\n\n## Workspace And Project Resolution\n\n1. Treat the current directory as the workspace starting point.\n2. Resolve the active project named by the user and locate its repository root.\n3. Read the project `AGENTS.md` and project brief or MemoryBank overview when\n   present before editing.\n4. Resolve the active project:\n   - `HEPHA`, `Hepha`, and `AgenticDevelopmentProcess` map to\n     `\u003Cworkspace root>\u002FAgenticDevelopmentProcess`.\n   - If the user names another project, use `docs\u002Fprojects.md` or the nearest\n     child repo folder matching that name.\n5. Read the child project `AGENTS.md` and `README.md` when present.\n6. Run project git, build, test, and edit commands from the child project root,\n   not from the parent workspace.\n\n## MemoryBank Resolution\n\nResolve the MemoryBank in this order:\n\n1. User-supplied MemoryBank path, if present.\n2. `.hepha\u002Fprojects.json` in the child project, matching project `name`, `id`,\n   or child root path.\n3. `\u003Cchild project root>\u002FMemoryBank` when it contains `Features\u002F`.\n4. A direct search under the child root for `MemoryBank\u002FFeatures`.\n\nStop with a blocker if no MemoryBank with `Features\u002F` exists.\n\n## FEAT Resolution\n\n1. Normalize the requested FEAT id to uppercase, for example `FEAT-002`.\n2. Search these folders under `\u003CMemoryBank>\u002FFeatures`:\n   - `03_IN_PROGRESS` first;\n   - then `02_READY_TO_DEVELOP`, `01_SUBMITTED`, `04_COMPLETED`, and\n     `05_CANCELLED` only for diagnostics.\n3. Match a FEAT folder by folder name or by `FeatureDescription.md` content.\n4. Continue implementation only when the FEAT is in `03_IN_PROGRESS`.\n5. Require `FeatureDescription.md`, `FeatureTasks.md`,\n   `PhaseExecutionContract.json`, and every phase document declared by that\n   contract.\n6. If the FEAT contains `[NEEDS VALIDATION]`, stop and report the exact file and\n   line references. Do not implement while validation markers remain.\n\n## Phase Resolution\n\nBuild the phase inventory before editing. `PhaseExecutionContract.json` is the\nonly source of topology and ordering. Do not infer execution order from a\nMarkdown title, filename, or display number:\n\n1. Read `FeatureTasks.md`.\n2. Read and validate `PhaseExecutionContract.json`, then read exactly the phase\n   documents declared there.\n3. Parse phase status from the `FeatureTasks.md` contract inventory first, then from\n   a phase file status line such as `**Status:** COMPLETED`.\n4. Normalize statuses:\n   - `Completed`, `Complete` -> `COMPLETED`\n   - `Skipped`, `N\u002FA` -> `SKIPPED`\n   - `Not Started`, `NOT_STARTED`, `Pending` -> `PENDING`\n   - `In Progress` -> `IN_PROGRESS`\n   - `Awaiting Review` -> `AWAITING_REVIEW`\n   - `Code Review In Progress` -> `CODE_REVIEW_IN_PROGRESS`\n   - `Awaiting User Acceptance` -> `AWAITING_USER_ACCEPTANCE`\n   - `Blocked`, `Failed`, `Rejected` -> `BLOCKED`\n5. Stop with a blocker if the execution contract is missing, invalid, or its\n   declared documents do not match the `Phases\u002F` directory.\n6. The current phase is the first contract-ordered phase that is not `COMPLETED` or\n   `SKIPPED`, unless a review-finding report clearly requires returning to a\n   specific earlier phase.\n7. If every contract phase is `COMPLETED` or `SKIPPED`, scan each phase's\n   `## Quality Gate Evidence` table. If any gate decision is `missing`, treat\n   the first contract-ordered phase with a missing gate as the current phase for\n   quality-gate repair only.\n\n## Autonomous Phase Loop\n\nWhen the user says `autonomous`, continue through phases in execution-contract order:\n\n1. Start at the current unresolved phase.\n2. Complete or skip only that phase's scoped work.\n3. Update durable task evidence and narrative notes in the phase document. Hepha owns lifecycle\u002Fstatus fields and FeatureTasks status cells.\n4. Run focused verification.\n5. Run review when needCodeReview is true.\n6. Fix blocking review findings and rerun focused verification.\n7. Record completion or skip evidence; Hepha deterministically writes `COMPLETED` or `SKIPPED` after validating it.\n8. Rescan phases from disk.\n9. Continue to the next unresolved contract phase.\n\nStop only when:\n\n- all declared contract phases are `COMPLETED` or `SKIPPED`;\n- all phase quality gates are `satisfied`, `waived`, or `not applicable`;\n- a real blocker requires human judgment;\n- credentials, permissions, missing dependency, or unsafe action prevents safe\n  progress;\n- the same failure repeats after a documented focused recovery attempt.\n\n## Per-Phase Work Rules\n\nBefore changing code in a phase:\n\n- Read the phase document.\n- Read `planning-analysis-report.md` whenever the current contract phase's\n  planning-index row identifies it as required context.\n- Read relevant parent EPIC and FEAT acceptance criteria, including linked\n  `EpicAcceptanceTests.md` scenarios and the current phase's `EPIC Acceptance\n  Traceability` assignments in `FeatureTasks.md` when present.\n- Read applicable `MemoryBank\u002FLessonsLearned` documents.\n- Inspect current git status from the child project root.\n- Preserve existing checked Markdown checklist items.\n- If the phase has no checkbox ledger, add a compact `## Phase Task Ledger`\n  before substantive work.\n\nDuring implementation:\n\n- Work only the current phase scope.\n- Skip checked tasks unless a changed file, failed verification, or review\n  finding explicitly invalidates them.\n- Do not edit reserved machine fields: `**Status:**`, FeatureTasks Status cells, or Quality Gate Evidence Decision cells. Hepha writes them from durable workflow events.\n- Record task progress and evidence; Hepha applies the lifecycle transition.\n- Do not broaden scope to dashboard\u002FUI\u002Fsync behavior unless the phase explicitly\n  requires it.\n- Do not move the FEAT folder between MemoryBank state folders.\n- Do not start dev servers, watch commands, or long-running UI processes.\n- Do not push to remotes.\n- Do not revert unrelated user changes.\n\n## Verification Rules\n\nApply the `serialized-build-commands` skill when available before running build,\ntest, lint, format, Cargo, pnpm, npm, or other shared-state commands.\n\nRun one verification command at a time. Wait for the result, inspect it, then\ndecide the next command.\n\nPrefer focused phase verification first. Run broad verification only when the\nphase or final checkpoint requires it and the narrower checks are green.\n\nDo not invent test results. Record exact commands and observed outcomes in the\nphase evidence.\n\nWhen a phase-selected validation fails and the phase declares\n`repair_and_rerun`, repair the directly responsible production code, test,\nfixture, configuration, or shared contract, then rerun the validation. The\nexpected-file list is a delivery forecast; it does not authorize relabelling a\nconfigured failure as out of scope or complete.\n\nThe final `## Hepha Gate Evidence Handoff` must use the exact three-column\n`Gate | Result | Evidence` schema. Changed files use `recorded`; Tests and\nGherkin\u002FPlaywright E2E use exactly `passed`, `failed`, or `not_applicable`.\nFailed, timed-out, skipped, or crashing required checks use `failed` and cannot\ncomplete the active task.\n\nThe phase declarations are authoritative: needCodeReview and needTestCoverage are independent booleans; all four combinations are valid. Ordered native tasks and explicit configured checks retain their own obligations. Phase identifiers, positions, titles and file types never select gates. Developers can revise declarations with before\u002Fafter values, implemented scope, reason and evidence, without hiding failures. Reuse valid evidence for unchanged inputs. Ordinary missing tests or rejected reviews remain same-phase repair work; escalate only a concrete impasse or repeated lack of a meaningful repair path.\n\n## Phase Quality Gate Evidence\n\nAgents write evidence in phase documents. Hepha owns the machine-readable\nlifecycle fields (`**Status:**` and FeatureTasks Status) and Quality Gate\nDecision cells. Do not alter those reserved fields. New phase documents created\nby RefineFeature use this table:\n\n| Gate | Decision | Evidence \u002F Justification |\n| --- | --- | --- |\n| Changed files | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Use `satisfied` when the exact changed paths are recorded; use a justified waiver only where appropriate. |\n| Tests | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Exact test files and commands, or a waiver explaining why tests are not useful for this phase. |\n| Gherkin\u002FPlaywright E2E | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Required only at the explicitly assigned workflow execution owner; retain EPIC E2E updates and execution links alongside phase TwinTests. |\n| Code review | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Phase review report path, or an explicit waiver and risk rationale. |\n\nRules:\n\n- Hepha writes Decision cells using exactly one canonical value: `missing`, `satisfied`, `waived`, or `not applicable`. Do not put synonyms such as `pass`, `passed`, `recorded`, `complete`, or `approved` in the Decision cell.\n\n- Keep every Quality Gate Evidence entry on exactly one physical Markdown table row: it must start and end with `|` and contain the three template columns. Put all evidence in the third cell on that same line; never wrap or continue a gate row onto a following line.\n\n- Follow the declared coverage and review flags with scope reasons for N\u002FA. Execute independently required checks even when both flags are false.\n- UI changes may require frontend TwinTests and EPIC E2E updates. Run full-workflow E2E at its declared owner; a passing TwinTest never waives it.\n- Do not claim a phase is complete with a required `missing` gate. Supply the\n  missing evidence or justification and let Hepha retain the lifecycle state.\n- Do not mark a phase complete while an EPIC acceptance scenario assigned to\n  that phase lacks its planned executable evidence or an exact documented\n  existing-coverage mapping.\n\n## Quality-Gate Repair Mode\n\nWhen all implementation phase work is already completed but one or more phase\nquality gates are `missing`, do not redo completed implementation tasks. Work\nonly the missing gates:\n\n- Missing `Code review`: inspect the declared review obligation and existing report. When required, repair findings and obtain approval for the applicable scope. If scope changed, record a justified declaration revision; do not infer review applicability from file types or directly overwrite machine-owned decision cells.\n- Missing `Tests`: inspect the declared acceptance coverage and required commands. Reuse valid execution and assertion evidence, repair missing meaningful coverage, and execute missing or invalidated required checks. A justified declaration revision must preserve actual failures and the remaining obligations.\n- Missing `Gherkin\u002FPlaywright E2E`: inspect the assigned workflow obligation and original execution evidence. Repair and execute that obligation at its declared owner; isolated tests cannot replace a required full-workflow check.\n- Preserve completed phase implementation task checkboxes. Do not broaden scope\n  beyond the missing gate unless a review finding requires a fix.\n\n## Review Rules\n\nWhen needCodeReview is true:\n\n1. Perform a dedicated review pass after implementation and focused checks.\n2. Review changed files first, then required phase\u002Fstatus\u002Fevidence context.\n3. Write a concise review report under the FEAT folder's `code-reviews\u002F`\n   directory when the project convention uses review artifacts.\n4. Treat BLOCKER\u002FREQUIRED findings as mandatory fixes.\n5. Evaluate notes and polish findings explicitly as fixed, deferred,\n   accepted-risk, rebutted, or follow-up.\n6. Do not mark the phase complete while blocking findings remain.\n\nIf a previous review report exists for the current phase and says\n`NEEDS_CHANGES`, begin by resolving those findings instead of restarting normal\nimplementation.\n\n## Output Contract\n\nAt the end of the run, report:\n\n- project root and MemoryBank path used;\n- FEAT id and folder;\n- phases completed\u002Fskipped during this run;\n- current phase after the run;\n- verification commands and results;\n- blocker, if any;\n- changed files.\n\nKeep the final summary concise and concrete.\n","# Continue Implementation\n\n## Model Authority\n\nThis procedure is model-neutral. When invoked directly, execution is\n`direct_host` and remains in the current Pi, Codex, or Claude Code session; that\nactive host owns model selection. Do not query Hepha routing policy, request a\nmodel switch, automatically hand off, choose a fallback model, or fabricate\nroute-policy evidence. Direct execution does not fabricate an orchestrated\nreceipt. Only an explicit Hepha launcher or dashboard dispatch creates a\nseparate `orchestrated` worker, whose route is injected outside this skill.\n\nYou are executing the HEPHA `continue-implementing` workflow directly from Pi.\n\nThis skill is for the direct Pi workflow, not for clicking the dashboard. It\nmust work when Pi is opened from a registered project or a parent workspace and\nthe user names the active project and a FEAT id such as `FEAT-002`.\n\n## Objective\n\nResolve the active HEPHA project and MemoryBank, locate the requested FEAT, read\nits `PhaseExecutionContract.json`, and continue the first unresolved declared\nphase autonomously in contract order until every declared phase is `COMPLETED`\nor `SKIPPED`, or until a real blocker requires human input.\n\n## Required Inputs\n\nAccept these from the user's message:\n\n- project name or alias, such as `HEPHA`, `Hepha`, or `AgenticDevelopmentProcess`;\n- FEAT id, such as `FEAT-002`;\n- optional MemoryBank path override;\n- optional mode, where `autonomous` means continue through subsequent phases\n  without stopping after one phase.\n\nIf the FEAT id is missing, ask one concise question. Otherwise, infer safely.\n\n## Workspace And Project Resolution\n\n1. Treat the current directory as the workspace starting point.\n2. Resolve the active project named by the user and locate its repository root.\n3. Read the project `AGENTS.md` and project brief or MemoryBank overview when\n   present before editing.\n4. Resolve the active project:\n   - `HEPHA`, `Hepha`, and `AgenticDevelopmentProcess` map to\n     `\u003Cworkspace root>\u002FAgenticDevelopmentProcess`.\n   - If the user names another project, use `docs\u002Fprojects.md` or the nearest\n     child repo folder matching that name.\n5. Read the child project `AGENTS.md` and `README.md` when present.\n6. Run project git, build, test, and edit commands from the child project root,\n   not from the parent workspace.\n\n## MemoryBank Resolution\n\nResolve the MemoryBank in this order:\n\n1. User-supplied MemoryBank path, if present.\n2. `.hepha\u002Fprojects.json` in the child project, matching project `name`, `id`,\n   or child root path.\n3. `\u003Cchild project root>\u002FMemoryBank` when it contains `Features\u002F`.\n4. A direct search under the child root for `MemoryBank\u002FFeatures`.\n\nStop with a blocker if no MemoryBank with `Features\u002F` exists.\n\n## FEAT Resolution\n\n1. Normalize the requested FEAT id to uppercase, for example `FEAT-002`.\n2. Search these folders under `\u003CMemoryBank>\u002FFeatures`:\n   - `03_IN_PROGRESS` first;\n   - then `02_READY_TO_DEVELOP`, `01_SUBMITTED`, `04_COMPLETED`, and\n     `05_CANCELLED` only for diagnostics.\n3. Match a FEAT folder by folder name or by `FeatureDescription.md` content.\n4. Continue implementation only when the FEAT is in `03_IN_PROGRESS`.\n5. Require `FeatureDescription.md`, `FeatureTasks.md`,\n   `PhaseExecutionContract.json`, and every phase document declared by that\n   contract.\n6. If the FEAT contains `[NEEDS VALIDATION]`, stop and report the exact file and\n   line references. Do not implement while validation markers remain.\n\n## Phase Resolution\n\nBuild the phase inventory before editing. `PhaseExecutionContract.json` is the\nonly source of topology and ordering. Do not infer execution order from a\nMarkdown title, filename, or display number:\n\n1. Read `FeatureTasks.md`.\n2. Read and validate `PhaseExecutionContract.json`, then read exactly the phase\n   documents declared there.\n3. Parse phase status from the `FeatureTasks.md` contract inventory first, then from\n   a phase file status line such as `**Status:** COMPLETED`.\n4. Normalize statuses:\n   - `Completed`, `Complete` -> `COMPLETED`\n   - `Skipped`, `N\u002FA` -> `SKIPPED`\n   - `Not Started`, `NOT_STARTED`, `Pending` -> `PENDING`\n   - `In Progress` -> `IN_PROGRESS`\n   - `Awaiting Review` -> `AWAITING_REVIEW`\n   - `Code Review In Progress` -> `CODE_REVIEW_IN_PROGRESS`\n   - `Awaiting User Acceptance` -> `AWAITING_USER_ACCEPTANCE`\n   - `Blocked`, `Failed`, `Rejected` -> `BLOCKED`\n5. Stop with a blocker if the execution contract is missing, invalid, or its\n   declared documents do not match the `Phases\u002F` directory.\n6. The current phase is the first contract-ordered phase that is not `COMPLETED` or\n   `SKIPPED`, unless a review-finding report clearly requires returning to a\n   specific earlier phase.\n7. If every contract phase is `COMPLETED` or `SKIPPED`, scan each phase's\n   `## Quality Gate Evidence` table. If any gate decision is `missing`, treat\n   the first contract-ordered phase with a missing gate as the current phase for\n   quality-gate repair only.\n\n## Autonomous Phase Loop\n\nWhen the user says `autonomous`, continue through phases in execution-contract order:\n\n1. Start at the current unresolved phase.\n2. Complete or skip only that phase's scoped work.\n3. Update durable task evidence and narrative notes in the phase document. Hepha owns lifecycle\u002Fstatus fields and FeatureTasks status cells.\n4. Run focused verification.\n5. Run review when needCodeReview is true.\n6. Fix blocking review findings and rerun focused verification.\n7. Record completion or skip evidence; Hepha deterministically writes `COMPLETED` or `SKIPPED` after validating it.\n8. Rescan phases from disk.\n9. Continue to the next unresolved contract phase.\n\nStop only when:\n\n- all declared contract phases are `COMPLETED` or `SKIPPED`;\n- all phase quality gates are `satisfied`, `waived`, or `not applicable`;\n- a real blocker requires human judgment;\n- credentials, permissions, missing dependency, or unsafe action prevents safe\n  progress;\n- the same failure repeats after a documented focused recovery attempt.\n\n## Per-Phase Work Rules\n\nBefore changing code in a phase:\n\n- Read the phase document.\n- Read `planning-analysis-report.md` whenever the current contract phase's\n  planning-index row identifies it as required context.\n- Read relevant parent EPIC and FEAT acceptance criteria, including linked\n  `EpicAcceptanceTests.md` scenarios and the current phase's `EPIC Acceptance\n  Traceability` assignments in `FeatureTasks.md` when present.\n- Read applicable `MemoryBank\u002FLessonsLearned` documents.\n- Inspect current git status from the child project root.\n- Preserve existing checked Markdown checklist items.\n- If the phase has no checkbox ledger, add a compact `## Phase Task Ledger`\n  before substantive work.\n\nDuring implementation:\n\n- Work only the current phase scope.\n- Skip checked tasks unless a changed file, failed verification, or review\n  finding explicitly invalidates them.\n- Do not edit reserved machine fields: `**Status:**`, FeatureTasks Status cells, or Quality Gate Evidence Decision cells. Hepha writes them from durable workflow events.\n- Record task progress and evidence; Hepha applies the lifecycle transition.\n- Do not broaden scope to dashboard\u002FUI\u002Fsync behavior unless the phase explicitly\n  requires it.\n- Do not move the FEAT folder between MemoryBank state folders.\n- Do not start dev servers, watch commands, or long-running UI processes.\n- Do not push to remotes.\n- Do not revert unrelated user changes.\n\n## Verification Rules\n\nApply the `serialized-build-commands` skill when available before running build,\ntest, lint, format, Cargo, pnpm, npm, or other shared-state commands.\n\nRun one verification command at a time. Wait for the result, inspect it, then\ndecide the next command.\n\nPrefer focused phase verification first. Run broad verification only when the\nphase or final checkpoint requires it and the narrower checks are green.\n\nDo not invent test results. Record exact commands and observed outcomes in the\nphase evidence.\n\nWhen a phase-selected validation fails and the phase declares\n`repair_and_rerun`, repair the directly responsible production code, test,\nfixture, configuration, or shared contract, then rerun the validation. The\nexpected-file list is a delivery forecast; it does not authorize relabelling a\nconfigured failure as out of scope or complete.\n\nThe final `## Hepha Gate Evidence Handoff` must use the exact three-column\n`Gate | Result | Evidence` schema. Changed files use `recorded`; Tests and\nGherkin\u002FPlaywright E2E use exactly `passed`, `failed`, or `not_applicable`.\nFailed, timed-out, skipped, or crashing required checks use `failed` and cannot\ncomplete the active task.\n\nThe phase declarations are authoritative: needCodeReview and needTestCoverage are independent booleans; all four combinations are valid. Ordered native tasks and explicit configured checks retain their own obligations. Phase identifiers, positions, titles and file types never select gates. Developers can revise declarations with before\u002Fafter values, implemented scope, reason and evidence, without hiding failures. Reuse valid evidence for unchanged inputs. Ordinary missing tests or rejected reviews remain same-phase repair work; escalate only a concrete impasse or repeated lack of a meaningful repair path.\n\n## Phase Quality Gate Evidence\n\nAgents write evidence in phase documents. Hepha owns the machine-readable\nlifecycle fields (`**Status:**` and FeatureTasks Status) and Quality Gate\nDecision cells. Do not alter those reserved fields. New phase documents created\nby RefineFeature use this table:\n\n| Gate | Decision | Evidence \u002F Justification |\n| --- | --- | --- |\n| Changed files | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Use `satisfied` when the exact changed paths are recorded; use a justified waiver only where appropriate. |\n| Tests | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Exact test files and commands, or a waiver explaining why tests are not useful for this phase. |\n| Gherkin\u002FPlaywright E2E | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Required only at the explicitly assigned workflow execution owner; retain EPIC E2E updates and execution links alongside phase TwinTests. |\n| Code review | satisfied\u002Fwaived\u002Fnot applicable\u002Fmissing | Phase review report path, or an explicit waiver and risk rationale. |\n\nRules:\n\n- Hepha writes Decision cells using exactly one canonical value: `missing`, `satisfied`, `waived`, or `not applicable`. Do not put synonyms such as `pass`, `passed`, `recorded`, `complete`, or `approved` in the Decision cell.\n\n- Keep every Quality Gate Evidence entry on exactly one physical Markdown table row: it must start and end with `|` and contain the three template columns. Put all evidence in the third cell on that same line; never wrap or continue a gate row onto a following line.\n\n- Follow the declared coverage and review flags with scope reasons for N\u002FA. Execute independently required checks even when both flags are false.\n- UI changes may require frontend TwinTests and EPIC E2E updates. Run full-workflow E2E at its declared owner; a passing TwinTest never waives it.\n- Do not claim a phase is complete with a required `missing` gate. Supply the\n  missing evidence or justification and let Hepha retain the lifecycle state.\n- Do not mark a phase complete while an EPIC acceptance scenario assigned to\n  that phase lacks its planned executable evidence or an exact documented\n  existing-coverage mapping.\n\n## Quality-Gate Repair Mode\n\nWhen all implementation phase work is already completed but one or more phase\nquality gates are `missing`, do not redo completed implementation tasks. Work\nonly the missing gates:\n\n- Missing `Code review`: inspect the declared review obligation and existing report. When required, repair findings and obtain approval for the applicable scope. If scope changed, record a justified declaration revision; do not infer review applicability from file types or directly overwrite machine-owned decision cells.\n- Missing `Tests`: inspect the declared acceptance coverage and required commands. Reuse valid execution and assertion evidence, repair missing meaningful coverage, and execute missing or invalidated required checks. A justified declaration revision must preserve actual failures and the remaining obligations.\n- Missing `Gherkin\u002FPlaywright E2E`: inspect the assigned workflow obligation and original execution evidence. Repair and execute that obligation at its declared owner; isolated tests cannot replace a required full-workflow check.\n- Preserve completed phase implementation task checkboxes. Do not broaden scope\n  beyond the missing gate unless a review finding requires a fix.\n\n## Review Rules\n\nWhen needCodeReview is true:\n\n1. Perform a dedicated review pass after implementation and focused checks.\n2. Review changed files first, then required phase\u002Fstatus\u002Fevidence context.\n3. Write a concise review report under the FEAT folder's `code-reviews\u002F`\n   directory when the project convention uses review artifacts.\n4. Treat BLOCKER\u002FREQUIRED findings as mandatory fixes.\n5. Evaluate notes and polish findings explicitly as fixed, deferred,\n   accepted-risk, rebutted, or follow-up.\n6. Do not mark the phase complete while blocking findings remain.\n\nIf a previous review report exists for the current phase and says\n`NEEDS_CHANGES`, begin by resolving those findings instead of restarting normal\nimplementation.\n\n## Output Contract\n\nAt the end of the run, report:\n\n- project root and MemoryBank path used;\n- FEAT id and folder;\n- phases completed\u002Fskipped during this run;\n- current phase after the run;\n- verification commands and results;\n- blocker, if any;\n- changed files.\n\nKeep the final summary concise and concrete.\n",{"name":5,"description":7,"agent_action":24},"continue-implementing","master","57a527998225d4654bad4d3edb7380523849d28d","pi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fcontinue-implementation","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess","https:\u002F\u002Fgithub.com\u002Faboimpinto","2026-10-31 15:24:59",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add aboimpinto\u002FAgenticDevelopmentProcess --skill continue-implementation",{"tool":37,"command":38},"bunx","bunx skills add aboimpinto\u002FAgenticDevelopmentProcess --skill continue-implementation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add aboimpinto\u002FAgenticDevelopmentProcess --skill continue-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fcontinue-implementation\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7C6RES661REA4K3SSD410VM","serialized-build-commands","Agents should invoke this skill before running build, test, lint, or format commands that use shared caches, file locks, build directories, or package manager state. Use especially before Rust Cargo commands such as cargo check, cargo test, cargo clippy, cargo fmt, cargo build, or any shell command containing cargo.","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-serialized-build-commands\u002Fskills\u002Fserialized-build-commands\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7C6R9EFN2C4620CFRMM5SMK","submit-epic","Use when the user asks Pi to submit, create, or draft a new HEPHA EPIC directly from a registered project workspace, preserving the useful legacy DevCycle MCP submit-epic command, for example \"submit-epic for HEPHA build observability projection hooks\" or \"create a HEPHA EPIC titled Runtime Approval Gates\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fsubmit-epic\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7C6R5H2SW40BQ3GJ61SSFP4","start-feature","Use when the user asks Pi to start a HEPHA FEAT implementation, run start-feature, or run start-implementing for a READY FEAT from a registered project workspace, for example \"use the start-feature skill for FEAT-003\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fstart-feature\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7C6R0NN4CAK6VPMPJH4Y5K3","refine-feature","Use when the user asks Pi to run refine-feature, refine a HEPHA FEAT, create FeatureTasks and phase files, or move a clarified FEAT to Ready To Develop, for example \"refine-feature FEAT-004\" or \"Use the refine-feature skill for HEPHA FEAT-004\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Frefine-feature\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7C6QWEKWY4AEFDCBCXKE9E8","design-feature","Use when the user asks Pi to run design-feature, design a HEPHA FEAT, create UI requirements, or prepare UX\u002Fdesign artifacts for a FEAT, for example \"design-feature FEAT-004\" or \"Use the design-feature skill for HEPHA FEAT-004\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fdesign-feature\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7C6QSJEJ7GZP51CGKNPN27D","deep-dive","Use when the user asks Pi to run a HEPHA Deep-Dive for an EPIC or FEAT, gather Deep-Dive questions, or apply saved Deep-Dive answers to a MemoryBank document, for example \"use the deep-dive skill for HEPHA FEAT-004\".","https:\u002F\u002Fgithub.com\u002Faboimpinto\u002FAgenticDevelopmentProcess\u002Fblob\u002Fmaster\u002Fpi-packages\u002Fpi-skill-hepha-continue-implementation\u002Fskills\u002Fdeep-dive\u002FSKILL.md",[],[]]