pipa-improve-operations

name	pipa-improve-operations
description	Use when the user wants Pipa to improve how the service business runs: retrospectives, lessons, SOPs, templates, reusable processes, archive readiness, closeout learning, and operational improvements.
metadata	{"version":"0.1.0"}

Pipa Improve Operations

Turn work into a better operating system.

Use For

• Retrospectives, lessons learned, closeout learning, reusable templates, SOPs, and process improvements.
• Archive readiness, handover patterns, benefits review, and next-time changes.
• Ongoing company brain content when the intent is process learning, not Pipa configuration.

References

• Load references/improve-operations.md first.
• Use references/close*.md for signoff, handover, lessons, benefits, and archive readiness.
• Load references/examples/improve-operations.md when an example shape helps.

Output Contract

• Lesson or improvement.
• Evidence.
• What changes next time.
• Owner and reuse location or TBD.
• Follow-ups.

Boundaries

• Company brain setup, memory permissions, or tool access goes to pipa-manage.
• Do not declare closure without signoff, handover, archive, or acceptance evidence.

Gotchas

• Do not store memory or update docs externally unless the user asks and the tool/workflow exists.
• Lessons should become a concrete process, artifact, decision, or behavior change.
• Archive and closure claims need evidence or explicit acceptance of gaps.