purge-initiative-artifacts-meta
Skill2 starsChanged 4 months agoMITView on GitHub
PM-lane purge: delete allowlisted meta working papers (Validation-Report, Resolution) for one initiative. Refuse KEEP paths (PRD, Impact-Map). Commit via Forge when pin requires it. No report file — success is handoff only. Independent of app/eng purge. No authorize-before-delete. Use Enter-at or /purge-initiative-artifacts-meta when the meta closure hop is due.
In this repository22 other files it gives its agents.
- ground-specSkill
- initiative-feasibilitySkill
- learning-extractSkill
- loop-specSkill
- pre-implementSkill
- purge-initiative-artifacts-appSkill
- spec-draftSkill
- spec-implementation-planSkill
- spec-technical-reviewSkill
- ensure-repo-graphSkill
- post-product-questionsSkill
- prd-codebase-mapSkill
- review-product-questionsSkill
- commit-workspaceSkill
- create-board-ticketsSkill
- open-draft-prSkill
- prd-impact-mapSkill
- prd-qualitySkill
- prd-thinkSkill
- review-findingsSkill
- update-documentsSkill
- validate-requirementsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Delete PURGE-set files under the meta repo for one initiative.
- Distinctive: line 21
Do not: delete durable KEEP roots.
- Distinctive: line 35
Delete only when present:
- Very specific: line 47
No Gateflow authorize-before-delete.
- Very specific: line 48
No report file: Do not write Purge-*.md (or any new artifact) under {reports_dir}.
- Distinctive: line 85
Use references/output-template.md (handoff only).
- Very specific: line 95
When handoff_path is bound, overwrite that path with the same handoff: envelope before exit.
- Very specific: line 101
When next is an external-action with open_draft_pr, fill handoff.forge per pin requires.
- Very specific: line 104
Never create Purge-*.md under reports.
- Very specific: line 105
Follow prayog-skills/references/forge-side-effects.md#content-producers when pin forge.commit_workspace is not disabled or next is an …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purge initiative artifacts (meta)
Lane: PM / meta repo (profile: meta-pm).
Delete PURGE-set files under the meta repo for one initiative. Do not delete durable KEEP roots. Git history remains the archive.
This skill is independent of app/engineering purge. Do not require, invoke,
or document /purge-initiative-artifacts-app as a prerequisite or prior step —
orchestration order lives only in pinned workflow.yaml.
Normative allowlist / refuse:
prayog-skills/references/artifact-write-contract.md.
NON-NEGOTIABLE
- Resolve layout from
.harness/profile.yamlor references/layout-defaults.md. - Require initiative id
INIT-*. Scope deletes to that initiative only. - Delete only when present:
{reports_dir}/Validation-Report-{INIT}.md{reports_dir}/Resolution-{INIT}.md
- Refuse (never delete):
prd/INIT-*.mdfor this initiative;{reports_dir}/Impact-Map-{INIT}.md; service catalog; governance. - Idempotent: missing allowlisted files → ok. Empty delete set → still
passwith rationale in handoff signals. - Workspace is the meta checkout (Gateflow binds meta root; human runs in
meta clone). Fill
handoff.forgeforcommit_workspacewhen pin requires it. When pin next is anopen_draft_prexternal-action, fill title and forge requires without creating a reports/ purge file (see output template). - No Gateflow authorize-before-delete. No merge. Never apply
*-lgtm. - No report file. Do not write
Purge-*.md(or any new artifact) under{reports_dir}. Goal achieved = handoff envelope (+ baton when bound) with delete/refuse lists insignals. Chat may repeat the same summary. - Dual-walker parity with human
/purge-initiative-artifacts-meta.
Inputs
- Initiative id — (REQUIRED)
- Workspace — meta repo root (REQUIRED)
- Layout — profile or layout-defaults
- Handoff baton — when
handoff_pathbound
Process
- T0 — resolve INIT and reports_dir; list allowlist candidates.
- T1 — classify delete / missing_ok / refused.
- T2 — delete delete-set only.
- T3 — emit handoff only (
stage: purge-initiative-artifacts-meta); no reports file. - T4 — fill
handoff.forgeforcommit_workspaceand, when pin next isopen_draft_pr, for that action (title + body from signals — no reports path).
Outcome selection
Map evidence to pinned workflow.yaml for this stage. Do not hardcode sibling
skill names as procedure dependencies.
| Outcome | When |
pass | Allowlist processed; no KEEP deleted; handoff emitted with signals |
needs-input | Initiative id or layout unreadable |
blocked | Attempt would touch KEEP |
failed | Delete/IO error |
Output
Use references/output-template.md (handoff only). Checks: references/checks.md.
Workflow handoff
- Emit envelope from
prayog-skills/references/handoff-envelope.md. Stagepurge-initiative-artifacts-meta. Setartifact.path: null(no durable report). Put path lists undersignals(deleted,missing_ok,refused, counts). Optionally setsignals.pr_bodyto a short markdown summary for Forge/PR consumers. - When
handoff_pathis bound, overwrite that path with the samehandoff:envelope before exit. - Derive
next_candidates,human_checkpoint, andexternal_actionfrom pinnedworkflow.yamlfor(stage: purge-initiative-artifacts-meta, outcome). Sethuman_checkpoint: trueonly when the resolved next node'stypeishuman-checkpoint. - When next is an
external-actionwithopen_draft_pr, fillhandoff.forgeper pinrequires. Prefer synthesizing PR body fromsignals/pr_body(runner may materialize an ephemeral body file outside{reports_dir}). Never createPurge-*.mdunder reports. - Follow
prayog-skills/references/forge-side-effects.md#content-producerswhen pinforge.commit_workspaceis notdisabledor next is an external-action.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

