Conduct First Portability Review of Blog Posting Guidelines

Task Library

Run the pilot portability review on the Blog Posting Guidelines – separate its methodology from its tool-specific steps and document the worked pattern for every other SOP.

Category: Knowledge System Maintenance

Use this when implementing Platform Portability Discipline – this Implementation Checklist task is a gap: /blog-posting-guidelines is the designated pilot, and no SOP has yet been through the separation.

Inputs

  • /blog-posting-guidelines – the full numbered process (Steps 1-17, from video upload through final QA)
  • The two-layer method (separate-methodology-layer-what-why-from-implementation-layer-how)
  • The SOP Amendment Proposal pipeline (the restructure ships through it)

Steps

  1. Open /blog-posting-guidelines and walk every numbered step (1-17), classifying each instruction as methodology (what/why: "transcribe the video and correct every error," "add internal links following the entity-linking decision tree") or implementation (how: Descript and its blue-underlined words, Grammarly/ChatGPT proofing, RankMath scores, LinkWhisper suggestions, WordPress block editor specifics).
  2. Note why this article is the pilot: it is dense with named tools, so it stress-tests the discipline – if separation works here, it works anywhere.
  3. Restructure each step so the methodology line leads and the tool-specific execution sits beneath it as a clearly labeled implementation block. Delete nothing – the tool detail is what makes the SOP runnable today; it just must be swappable tomorrow.
  4. Run the portability test: with all implementation blocks removed, Steps 1-17 must still describe a complete, executable content process on any equivalent toolchain. Patch methodology gaps the test exposes.
  5. Ship the restructure through the SOP Update Protocol: amendment proposal(s) within the 500-word format (split by section if needed), weekly senior review, version increment, changelog entry.
  6. Document the worked pattern – classification calls that were hard, formatting choices, time taken – as the pilot playbook for review-existing-sops-for-portability-compliance to apply across the rest of the library.
  7. Capture lessons as Knowledge Capture Notes within 24 hours of finishing; the pilot's purpose is to teach the system, not just fix one article.

Definition of done (QA checklist)

  • All numbered steps of /blog-posting-guidelines classified with zero unlabeled mixed instructions remaining
  • Portability test passed: methodology layer alone still teaches the full process; no tool detail deleted, only layered
  • Restructure approved via SOP Amendment Proposal(s) with version increment and changelog
  • Pilot playbook documented and handed to the library-wide compliance review
  • Lessons filed as Knowledge Capture Notes within 24 hours
  • Linked back to the definitive article and relevant siblings
  • Complies with Blog Posting Guidelines (if it publishes content)

Example(s)

  • /knowledge-system-maintenance – the Implementation Checklist names Blog Posting Guidelines as the portability pilot; /blog-posting-guidelines is the document under review.
  • Example needed – run the Meta-Article Prompt (/meta-article-prompt-template) after the pilot ships and link the meta-article here.

File in the zip: skills/knowledge-system-maintenance/conduct-first-portability-review-of-blog-posting-guidelines.md. Download the Task Library zip.

Index: Task Library. Article guidelines.

Scroll to Top