Problem Statement
The organization needs a structured workflow to inventory existing prompts and establish a maintainable prompt management system. The goal is to create a clear taxonomy, versioning rules, governance workflow, documentation standards, and deprecation policies while ensuring security and engineering-friendly processes. This will prevent prompt sprawl, reduce confusion, and support long-term maintainability.
Steps
Prompt Inventory Collection
INGESTIngest all existing prompts along with associated metadata such as use cases, owners, update frequency, and any known risks. Normalize formats for downstream use.
Taxonomy and Folder Structure Definition
EXECUTEGenerate a clean folder/tag taxonomy based on use cases, owners, and prompt categories. Ensure the structure is process-light and easy for engineers to maintain.
Metadata and Documentation Drafting
EXECUTECreate standardized metadata fields and documentation templates for each prompt, including test cases, owners, versioning info, and constraints such as no secrets.
Governance and Approval Workflow Validation
EXECUTEDefine versioning rules, review/approval steps, and deprecation policies. Validate that they meet engineering, security, and maintainability standards.
Implementation Guidelines Generation
EXECUTEProduce implementation guidance explaining how teams should adopt the taxonomy, documentation template, and governance rules.
Ongoing Maintenance Plan
EXECUTEOutline how prompts will be reviewed, updated, deprecated, or retired over time based on change frequency and owner responsibilities.
Prompt Configurations
Governance Drafting Prompt
You are creating engineering-friendly governance rules for prompt management. Produce versioning guidelines, a lightweight approval workflow, and a tidy deprecation policy. Constraints: do not include any secrets, ensure rules are public-safe, and include test-case expectations for each prompt. Tone: tidy, concise, engineering-minded. Only use the information provided; do not invent organizational details.
Taxonomy Generation Prompt
Given a list of prompts with their use cases, owners, and change frequency, produce a clean folder/tag taxonomy. Ensure it is simple, scalable, and avoids overlap. Tone should be process-light and engineering-friendly. Do not fabricate data; only reorganize what is provided.
Example Inputs/Outputs
Prompts: onboarding_support.json (owner: CS Ops, changes monthly), lead_scoring_prompt.md (owner: Growth, changes quarterly). Use cases provided. Request: generate taxonomy + versioning rules.
Proposed taxonomy: /customer_support/onboarding/, /growth/lead_scoring/. Versioning: semantic versioning with required review for minor and major changes. Deprecation policy: mark as deprecated for 30 days before removal, with owner notification. Documentation template includes fields for owner, use case, change frequency, test cases, and no-secrets confirmation.