Sync strategy documentation with shipped features from Linear and light specs.
npx skills add https://github.com/withpiper/pipekit --skill strategy-sync-withpiper
Please help me install this Agent Skill. Skill: strategy-sync Source: https://github.com/withpiper/pipekit/tree/main/skills/10-strategy-sync Command: npx skills add https://github.com/withpiper/pipekit --skill strategy-sync-withpiper
Strategy docs often drift from what is actually built. This skill updates Strategy docs to reflect shipped features, ensuring readers understand the product today, not just the originally envisioned plan.
Initiate a strategy-sync to align Strategy docs with shipped features.
High-intent search queries and answers about installing and using this skill.
To sync strategy docs with shipped features, the strategy-sync process compares your shipped work from Linear and code against a strategy docs manifest, producing versioned updates that eliminate documentation drift. It reads current implementation to ensure documentation reflects the product today.
Strategy documentation drift occurs when technical strategy docs no longer match the actually built features. You prevent it by enforcing versioned updates and cross-doc consistency checks across Conceptual Overview, Technical Architecture, and Permissions sections whenever new features ship.
Yes, you need a strategy docs manifest like method.config.md to maintain cross-document consistency. The sync process reads this manifest to compare shipped features against current implementation and apply audience-aware edits across multiple strategy documentation sections.
To update technical architecture docs when features ship in Linear, you run a strategy-sync that reads shipped Linear work and light specs, comparing them against your manifest to generate versioned governance updates for stakeholders and developers.
Yes, you can automate versioned updates for strategy governance documentation. The sync mechanism reads shipped features and current implementation to produce audience-aware edits, ensuring stakeholders always reference accurate, versioned strategy content rather than the originally envisioned plan.
A limitation of using a strategy docs manifest for sync is that it requires a method.config.md file to function. Without this manifest, the process cannot read shipped work or compare implementation to produce the necessary versioned updates and cross-doc consistency edits.
jperezdelrealGenerate mesh.json manifests and copy sync scripts for distributed squad coordination.
spencerbeggsAlign design documentation with current codebase architecture and flag unsafe changes.
warpdotdevPlan and execute feature implementations while keeping specs aligned with code changes.
openharmonyinsightCheck OpenHarmony API documentation for template compliance and consistency against d.ts declarations.
