feat(skills): add the feature-parity-alignment skill (5x2x3 parity Feature Package playbook)

[andrexibiza]

feat(skills): add feature-parity-alignment-campaigns skill (5x2x3 parity Feature Package playbook)

What this is

The reusable playbook for the platform Feature Parity & Alignment Campaigns Axl ordered with the same surgical precision as the Telegram Feature Package (#78791). Proven live on four platforms, all measured:

Platform	tracker	Adapter @ craft	Lane shape
Telegram	#78791	10,147 lines	S1–S5 + G (10 mixins via #79010)
Discord	#79564	10,138 lines	S1–S5 + G
Slack	#79772	9,088 lines	S1–S4 + S5 @Hermes Tag flagship + G
WhatsApp	#79890	1,918 lines	S1–S5 + S6 decomposition/headroom (no G)

Encodes the full anatomy: Wave-0 recon (measured counts, dedup anchors) → craft → tracker filing → worktree hive → ledger classification (all open issues into lanes, dependency edges) → three-wave 5×2×3 blind analysis (gap catalogs GAP_UNSUPPORTED / GAP_PARTIAL / GAP_CONFLICTED / GAP_DOCS / GAP_BUG_TRACKED) → decomposition lane execution (G lane for >2,000-line god-files; S6 under-ceiling headroom per Axl 2026-08-05: "the ceiling is not a target"). Plus the hard standards, deliverables checklist, and the pitfalls that cost real time on the Telegram/WhatsApp runs.

Interlock

Part of #78647 ( All Gods — repo-wide large-file decomposition tracker). This skill is the Feature Package-family sibling of the two locked skill PRs:

• Related feat(skills): add the large-file decomposition feature package skill (5x2x3 blind-witness decomposition) #79609 — feat(skills): add godfile--campaigns skill (5x2x3 blind-witness decomposition)
• Related docs(skills): document the kill-locks feature package and its tracker interlock #79779 — docs(skills): add Feature Package-operations--locks — LOCK doctrine interlocked to the -All-Gods tracker

Parity Feature Package metas it governs (each carries full lane/dependency ledgers): #78791 (Telegram) #79564 (Discord) #79772 (Slack) #79890 (WhatsApp).

Files

• skills/github/feature-parity-alignment-campaigns/SKILL.md — the playbook (88 lines, 2k-Law clean, progressive disclosure: lean SKILL.md + references/)
• skills/github/feature-parity-alignment-campaigns/references/template-epic-body.md — GitHub-ready tracker body template for future platform campaigns

Verification

• git diff --check clean, LF-only, DCO-signed.
• 88-line SKILL.md — 2k-Law compliant; reference file holds the template.
• Pattern matches feat(skills): add the large-file decomposition feature package skill (5x2x3 blind-witness decomposition) #79609/docs(skills): document the kill-locks feature package and its tracker interlock #79779: skill under skills/<category>/, PR body carries Part of [COMPLETE] Large-file decomposition: 20/20 done #78647 + Related list with every number, no ranges.

Part of #60535
Part of #80392

[andrexibiza]

Interlock: this skill joins the locked campaign-skill family — Part of #78647 (Kill All Gods, repo-wide epic).

• Related feat(skills): add the large-file decomposition feature package skill (5x2x3 blind-witness decomposition) #79609 — feat(skills): add godfile-kill-campaigns skill (5x2x3 blind-witness decomposition)
• Related docs(skills): document the kill-locks feature package and its tracker interlock #79779 — docs(skills): add campaign-operations-kill-locks — KILL LOCK doctrine interlocked to the Kill-All-Gods epic

Family: #79609 + #79779 + #79898. Same category pattern, same epic binding. The WeChat Feature Parity and Alignment Campaign meta-issue (filed under this playbook) joins as the fifth platform campaign: #78791 (Telegram), #79564 (Discord), #79772 (Slack), #79890 (WhatsApp).

[andrexibiza]

The long-document production skill and the canonical publication are now proposed in #80551.

This contribution is interlocked with the graph-gated engineering family:

• Part of [COMPLETE] Large-file decomposition: 20/20 done #78647
• Related feat(skills): add the large-file decomposition feature package skill (5x2x3 blind-witness decomposition) #79609 (godfile-kill-campaigns)
• Related docs(skills): document the kill-locks feature package and its tracker interlock #79779 (campaign-operations-kill-locks)
• Related feat(skills): add the feature-parity-alignment skill (5x2x3 parity Feature Package playbook) #79898 (Feature Parity & Alignment campaigns)
• Related feat(docs): cross-language docs germination pipeline — French automatic, top-10 languages manifest, CI gate #80391 (cross-language docs germination)
• Related [EPIC] Cross-Language Docs Germination — top-10 global languages, French first #80392 (cross-language docs germination EPIC)
• Related Add French translations for README and contributor docs #60535 / docs: add French translations (README, CONTRIBUTING, SECURITY) #63660 (French provenance and contributor authorship)

The repository contribution includes the skill under skills/research/, the guide under website/docs/guides/, the guide sidebar and llms.txt generator registration, the compiled 68-page PDF, LaTeX source, BibTeX, and a checked-in bidirectional interlock manifest.

Attribution is a core value: the contribution preserves Axl Ibiza, MBA’s authorship of the doctrine and publication, plus contributor, reviewer, agent, and source-project provenance.

PR: #80551
Signed-off-by: Andrex Ibiza, MBA 84248988+andrexibiza@users.noreply.github.com

[andrexibiza]

The long-document production skill and the canonical publication are now proposed in #80551.

This contribution is interlocked with the graph-gated engineering family:

• Part of [COMPLETE] Large-file decomposition: 20/20 done #78647
• Related feat(skills): add the large-file decomposition feature package skill (5x2x3 blind-witness decomposition) #79609 (godfile-kill-campaigns)
• Related docs(skills): document the kill-locks feature package and its tracker interlock #79779 (campaign-operations-kill-locks)
• Related feat(skills): add the feature-parity-alignment skill (5x2x3 parity Feature Package playbook) #79898 (Feature Parity & Alignment campaigns)
• Related feat(docs): cross-language docs germination pipeline — French automatic, top-10 languages manifest, CI gate #80391 (cross-language docs germination)
• Related [EPIC] Cross-Language Docs Germination — top-10 global languages, French first #80392 (cross-language docs germination EPIC)
• Related Add French translations for README and contributor docs #60535 / docs: add French translations (README, CONTRIBUTING, SECURITY) #63660 (French provenance and contributor authorship)

The repository contribution includes the skill under skills/research/, the guide under website/docs/guides/, the guide sidebar and llms.txt generator registration, the compiled 68-page PDF, LaTeX source, BibTeX, and a checked-in bidirectional interlock manifest.

Attribution is a core value: the contribution preserves Axl Ibiza, MBA’s authorship of the doctrine and publication, plus contributor, reviewer, agent, and source-project provenance.

PR: #80551
Signed-off-by: Andrex Ibiza, MBA 84248988+andrexibiza@users.noreply.github.com

[Enough1122]

AI code review — automated review for reference, author can ignore or act on any point.

feat(skills): add feature-parity-alignment-campaigns skill (5x2x3 parity Feature Package playbook)

Useful playbook that condenses hard-won campaign process into a repeatable skill. Observations against the repo's skill authoring standards:

1. skills/github/feature-parity-alignment-campaigns/SKILL.md — author attribution: frontmatter says author: Ares, but the contributor identity added in this PR is andrexibiza (Axl Ibiza). The repo's skill standard requires the human contributor's real name + GitHub handle first ("credit the human, not the tool"). Please change to something like Axl Ibiza (andrexibiza).
2. Local machine path leaked into a shipped skill: the Craft step instructs drafting the campaign file at D:/brain/AI-Systems-Intelligence/YYYY-MM-DD_<platform>-feature-parity-campaign.md — a path that only exists on the author's machine. A bundled skill must be portable: use a repo-relative or HERMES_HOME-relative location, or make it a configurable variable.
3. The "STANDING RULE (Axl, 2026-08-05)" block is a personal standing order embedded in a bundled skill's front matter. Even if the interlock behavior is desired, shipping a personal directive verbatim is unusual; consider converting it into a neutral "Campaign family interlock" section that states the policy without the personal framing.
4. Section order deviates from the repo standard (# Skill title, intro, ## When to Use, ## Prerequisites, ## How to Run, ## Quick Reference, ## Procedure, ## Pitfalls, ## Verification): this skill has Trigger/Anatomy/Deliverables/Standards/Pitfalls/Precedent metas but no ## When to Use, ## Prerequisites, or ## Verification. Given the playbook's complexity, a short ## Verification checklist (e.g. "ledger posted, all issues interlocked, zero orphans") would make completion objectively checkable.
5. The skill's headline interactions are gh search / gh issue create / git worktree add — third-party CLIs. The standards prefer native Hermes tools (search_files, terminal) as the named surface. This is a workflow skill where gh is arguably the domain tool, but consider naming the Hermes terminal wrapper where the intent is "run this command" vs a raw CLI, to stay consistent with the guideline.
6. contributors/emails/andrexibiza@users.noreply.github.com contains a # Axl Ibiza, MBA contributor identity comment line inside a file whose other entries are bare usernames — confirm the parser handling the emails directory tolerates comments (if it does, fine; if not, this entry will be misread).

[andrexibiza]

Superseded by #90307.

#79898 established the useful 5×2×3 campaign doctrine, but its current branch is stale/non-mergeable and the contract remains prose-only. #90307 preserves that doctrine and closes the deeper class with current-main executable enforcement:

• digest-locked capability identity and disposition;
• exact row cardinality/order;
• one authoritative publication per active capability;
• explicit runtime-consumer wiring;
• forbidden god-file growth;
• artifact-evidence versus delivery-state separation;
• exact merged-SHA, CI, live-receipt, and independent-review requirements for release.

The concrete Discord application is #90321. Closing this PR as superseded preserves its history and conceptual provenance; #90307 explicitly records the supersession.