@xaviele/ag-kit 1.0.0

package/template/.agent/skills/skills/mindrally-meta-prompt/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: "meta-prompt"
+description: "Meta-prompting framework for critiquing responses, analyzing solution trajectories, and evaluating AI-generated content quality"
+version: 1.0.0
+category: build
+---
+
+# Meta-Prompt
+
+A collection of meta-prompting techniques for evaluating and analyzing AI responses and solution paths.
+
+## Response Quality Evaluator
+
+A framework for critiquing and reflecting on the quality of responses, providing a score and indicating whether the response has fully solved the question or task.
+
+### Evaluation Fields
+
+**Reflections**: The critique and reflections on the sufficiency, superfluency, and general quality of the response.
+
+**Score**: Score from 0-10 on the quality of the candidate response.
+
+**Found_solution**: Whether the response has fully solved the question or task.
+
+### Evaluation Criteria
+
+When evaluating responses, consider the following:
+
+1. **Accuracy**: Does the response correctly address the question or task?
+2. **Completeness**: Does it cover all aspects of the question or task?
+3. **Clarity**: Is the response clear and easy to understand?
+4. **Conciseness**: Is the response appropriately concise without sacrificing important details?
+5. **Relevance**: Does the response stay focused on the question or task at hand?
+
+Provide thoughtful reflections on these aspects and any other relevant factors. Use the score to indicate the overall quality, and set found_solution to true only if the response fully addresses the question or completes the task.
+
+### Example Usage
+
+```
+reflections: "The response was clear and concise, addressing the main question effectively. However, it could have provided more context on edge cases."
+score: 8
+found_solution: true
+```
+
+## Question-Answering Trajectory Analyzer
+
+Guidelines for analyzing solution paths to question-answering tasks.
+
+### Trajectory Components
+
+**Observations**: Environmental information about the current situation that provides context for decision-making.
+
+**Thoughts**: Reasoning about the current situation, analyzing what has been observed and planning next steps.
+
+**Actions**: The steps taken to progress toward solving the task.
+
+### Action Types
+
+**Search[entity]**: Searches for the exact entity and returns relevant information if the entity exists. If not, returns suggestions for similar entities.
+
+**Lookup[keyword]**: Returns the next relevant passage that contains the keyword. Used for finding specific information within retrieved content.
+
+**Finish[answer]**: Returns the answer and finishes the task. Used when sufficient information has been gathered to provide a definitive response.
+
+### Analysis Guidelines
+
+When analyzing a trajectory:
+
+1. Evaluate whether each observation provides useful information
+2. Assess if thoughts demonstrate logical reasoning
+3. Determine if actions are appropriate given the current state
+4. Score the trajectory correctness from 1-10
+5. Evaluate reasoning validity even in incomplete trajectories
+6. Do not generate additional steps; only analyze what is provided
+
+## Prompt Engineering Patterns
+
+### Chain of Thought
+
+Guide the model through step-by-step reasoning:
+
+```
+Let's approach this step by step:
+1. First, identify the key components
+2. Then, analyze each component
+3. Finally, synthesize the findings
+```
+
+### Few-Shot Learning
+
+Provide examples to establish the pattern:
+
+```
+Example 1: [input] -> [output]
+Example 2: [input] -> [output]
+Now apply this pattern to: [new input]
+```
+
+### Self-Consistency
+
+Generate multiple reasoning paths and select the most consistent answer.
+
+### Reflection Prompts
+
+Encourage self-critique:
+
+```
+Review your response and identify:
+- Any potential errors or oversights
+- Areas that could be explained more clearly
+- Missing information that would strengthen the answer
+```
+
+## Quality Metrics
+
+### Response Scoring Rubric
+
+- **10**: Perfect response, fully addresses all aspects with exceptional clarity
+- **8-9**: Excellent response with minor room for improvement
+- **6-7**: Good response that addresses the main points but lacks depth
+- **4-5**: Adequate response with significant gaps or unclear explanations
+- **2-3**: Poor response that misses key aspects or contains errors
+- **0-1**: Response fails to address the question or is completely incorrect
+
+### Trajectory Scoring
+
+- **10**: Optimal path with efficient, logical steps
+- **7-9**: Good path with minor inefficiencies
+- **4-6**: Acceptable path but with unnecessary steps or missed opportunities
+- **1-3**: Poor path with fundamental reasoning errors

package/template/.agent/skills/skills/pm-skills-create-prd/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: "create-prd"
+description: "Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD."
+version: 1.0.0
+category: product
+---
+
+# Create a Product Requirements Document
+
+## Purpose
+
+You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.
+
+## Context
+
+A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.
+
+## Instructions
+
+1. **Gather Information**: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.
+
+2. **Think Step by Step**: Before writing, analyze:
+   - What problem are we solving?
+   - Who are we solving it for?
+   - How will we measure success?
+   - What are our constraints and assumptions?
+
+3. **Apply the PRD Template**: Create a document with these 8 sections:
+
+   **1. Summary** (2-3 sentences)
+   - What is this document about?
+
+   **2. Contacts**
+   - Name, role, and comment for key stakeholders
+
+   **3. Background**
+   - Context: What is this initiative about?
+   - Why now? Has something changed?
+   - Is this something that just recently became possible?
+
+   **4. Objective**
+   - What's the objective? Why does it matter?
+   - How will it benefit the company and customers?
+   - How does it align with vision and strategy?
+   - Key Results: How will you measure success? (Use SMART OKR format)
+
+   **5. Market Segment(s)**
+   - For whom are we building this?
+   - What constraints exist?
+   - Note: Markets are defined by people's problems/jobs, not demographics
+
+   **6. Value Proposition(s)**
+   - What customer jobs/needs are we addressing?
+   - What will customers gain?
+   - Which pains will they avoid?
+   - Which problems do we solve better than competitors?
+   - Consider the Value Curve framework
+
+   **7. Solution**
+   - 7.1 UX/Prototypes (wireframes, user flows)
+   - 7.2 Key Features (detailed feature descriptions)
+   - 7.3 Technology (optional, only if relevant)
+   - 7.4 Assumptions (what we believe but haven't proven)
+
+   **8. Release**
+   - How long could it take?
+   - What goes in the first version vs. future versions?
+   - Avoid exact dates; use relative timeframes
+
+4. **Use Accessible Language**: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
+
+5. **Structure Output**: Present the PRD as a well-formatted markdown document with clear headings and sections.
+
+6. **Save the Output**: If the PRD is substantial (which it will be), save it as a markdown document in the format: `PRD-[product-name].md`
+
+## Notes
+
+- Be specific and data-driven where possible
+- Link each section back to the overall strategy
+- Flag assumptions clearly so the team can validate them
+- Keep the document concise but complete
+
+---
+
+### Further Reading
+
+- [How to Write a Product Requirements Document? The Best PRD Template.](https://www.productcompass.pm/p/prd-template)
+- [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https://www.productcompass.pm/p/ai-prd-template)