Task Library
Ensure meta-articles separate the transferable general approach from the platform-specific details of that particular run, so documented agent work stays useful after tools change.
Category: Knowledge System Maintenance
Use this when writing or auditing meta-articles – the documented runs of real work created via /meta-article-prompt-template – so each one teaches a reusable method, not just a tour of one tool on one day.
Inputs
- The meta-article(s) to review, or the run about to be documented
- The two-layer standard from Process 4 (methodology = what/why; implementation = how)
- The Meta-Article Prompt Template (/meta-article-prompt-template)
Steps
- Pull the meta-articles in scope: existing ones linked from definitive articles as examples, and any new one being written from a fresh run.
- For each, check that it distinguishes the two layers: the general approach – what was done and why, the decisions and method any reader could transfer; and the platform-specific execution – the exact tools, versions, and steps used in this particular run.
- Where the layers are blended, add explicit framing rather than deleting detail: a short "the approach" passage stating the transferable method, and a clearly marked "how we ran it this time" passage holding the tool specifics. Meta-articles need the specifics – they are the proof – but labeled as that run's implementation.
- Run the reader test: someone on a different platform (different editor, ad manager, transcription tool) must still be able to extract and apply the method. If the method only makes sense inside the named tool, the methodology framing is missing.
- For future runs, push the fix upstream: if the Meta-Article Prompt Template does not already ask for approach-vs-execution separation, propose that addition via an SOP Amendment Proposal so every future meta-article is born portable.
- Record reviewed meta-articles and their fixes in the audit notes; recheck new meta-articles as part of the quarterly audit's example checks.
Definition of done (QA checklist)
- Every in-scope meta-article has clearly framed approach (transferable) and execution (this run's tools) layers
- Reader test passed: the method is extractable by someone on a different platform
- No proof-level detail deleted – specifics retained but labeled as implementation
- Template-level fix proposed via SOP Amendment if the Meta-Article Prompt lacks the separation requirement
- Reviewed articles and fixes recorded for the quarterly audit trail
- Linked back to the definitive article and relevant siblings
- Complies with Blog Posting Guidelines (if it publishes content)
Example(s)
- /meta-article-prompt-template – the canonical meta-article system this discipline applies to; /knowledge-system-maintenance Process 4 extends portability to these documents explicitly.
- Example needed – run the Meta-Article Prompt (/meta-article-prompt-template) after the first portability pass over a meta-article and link it here.
File in the zip: skills/knowledge-system-maintenance/apply-portability-discipline-to-meta-articles.md. Download the Task Library zip.
Index: Task Library. Article guidelines.