jarvis-ai-framework 1.0.0

package/skills/prod-roadmap-report/rules/detailed-guide.md

@@ -0,0 +1,237 @@
+# Project Status Report - Detailed Guide
+
+This file contains detailed examples, section guidelines, and edge cases for the project status report skill.
+
+Read `CLAUDE.md` and `memory/` in the working directory. If don't exist, suggest `/eis-pm-plugin:pm.memory` first.
+## Section Guidelines
+
+### Summary Paragraph
+
+- Write in prose, not bullet points
+- Max 200 words, divided in 2-4 paragraphs typical. Keep it concise but complete
+- Capture the main discussion topics, based on time discussed and how many times was cited in the discussed
+- Include context and key points
+- Use neutral, factual language
+### On Track
+
+- Items showing positive progress
+- Completed milestones
+- Things proceeding as planned
+- Format: **Bold topic name**: Description
+- If nothing is explicitly on track, use empty list or omit section
+- ignore this block in the final output if empty or don't have content
+### Problems
+
+- Current blockers
+- Active issues
+- Things not working as expected
+- Format: **Bold problem name**: Description
+- Only include explicitly mentioned problems
+- ignore this block in the final output if empty or don't have content
+
+### Risks & Concerns
+
+- Potential future problems
+- Uncertainties
+- Dependencies that might fail
+- When the topic is late or will re-scheduled
+- Format: **Bold concern/risk name**: Description
+- Only include explicitly mentioned concerns
+- ignore this block in the final output if empty or don't have content
+
+### Actions
+
+- Specific next steps
+- Assigned tasks (include assignee if mentioned)
+- Decisions that require follow-up
+- Simple list format
+- Only include explicitly stated actions
+- Don't invent actions
+
+## Historical Context Usage
+
+If previous reports or knowledge base information is available:
+
+- **Team name consistency**: Use established team names from previous reports
+- **Project naming**: Follow naming conventions from historical reports
+- **Recurring issues tracking**: Check if current problems were mentioned in previous reports
+- **Action item follow-up**: Cross-reference with previous action items to track completion
+- **Pattern recognition**: Identify recurring risks or concerns
+- **Context enrichment**: Use historical context to better understand abbreviations, codenames, or internal references
+
+**Important**: Historical context is used ONLY for:
+- Understanding terminology and naming patterns
+- Maintaining consistency with previous reports
+- Recognizing recurring themes
+
+**NEVER use historical context for:**
+- Inventing current status updates
+- Filling in missing information
+- Making assumptions about current progress
+
+## Update Workflow
+
+When updating an existing report:
+
+1. **Read original report carefully**: Note language, section structure, formatting choices
+2. **Preserve exact structure**: Keep the same headers, section order, and formatting style
+3. **Insert new content BEFORE old content**: Maintain reverse chronological order
+4. **Use current date**: DD-MM-YYYY format for new entry
+5. **Maintain language consistency**: Use same language as original report
+
+**Example of correct update structure:**
+
+**Existing report on 01-12-2025:**
+
+```markdown
+## Backend Team
+### Payment API
+
+#### 01-12-2025
+Database migration completed successfully. All endpoints tested and working.
+
+**On track:**
+- **Database migration**: Completed without downtime
+...
+```
+
+**New update on 02-12-2025:**
+
+```markdown
+## Backend Team
+### Payment API
+
+#### 02-12-2025
+Performance optimization implemented. Response times improved by 40%.
+
+**On track:**
+- **API performance**: Response time reduced from 500ms to 300ms
+...
+
+#### 01-12-2025
+Database migration completed successfully. All endpoints tested and working.
+
+**On track:**
+- **Database migration**: Completed without downtime
+...
+```
+
+New content is inserted BEFORE the old content, maintaining reverse chronological order.
+
+## Handling Edge Cases
+
+### Single Project, No Team Name
+
+```markdown
+## [Team Name To Be Defined]
+### {Project Name}
+#### {date}
+{content}
+```
+
+### Multiple Teams, Same Project
+
+Create separate sections for each team's perspective on the project.
+
+### No Clear Project Structure
+
+If the input is just general updates without clear project boundaries:
+
+1. Ask the user (in their language) if the update refers to a specific project or is a general team status
+2. Structure based on user response
+
+### Conflicting Information
+
+When there's conflicting information about status, dates, or other critical details:
+
+- Stop and ask the user (in their language) to clarify which information is correct, quoting both conflicting statements
+
+## Example Interactions
+
+### Example 1: Well-Structured Input
+
+**User provides:** Meeting transcription with clear team names, project discussions, problems, and actions.
+
+**Assistant should:**
+
+1. Extract all information
+2. Structure into template
+3. Generate complete markdown report
+4. No questions needed
+
+### Example 2: Ambiguous Input
+
+**User provides:** Slack messages with technical discussions but no clear team attribution.
+
+**Assistant should:**
+
+1. Extract technical content
+2. Organize into template structure
+3. Ask (in user's language) which team is responsible for this work
+4. Generate report after clarification
+
+### Example 3: Multiple Projects
+
+**User provides:** Long transcription covering 3 different initiatives.
+
+**Assistant should:**
+
+1. Identify the 3 initiatives
+2. Extract information for each
+3. Create single markdown with 3 sections (one per initiative)
+4. Follow template for each section
+
+### Example 4: Update Existing Report
+
+**User provides:** Previous report file + new meeting notes
+
+**Assistant should:**
+
+1. Read and analyze previous report structure (language, sections, format)
+2. Extract new information from meeting notes
+3. Merge new info into existing structure while preserving EXACT format
+4. Update date to current date
+5. Insert new content BEFORE old content (reverse chronological)
+6. Return updated report maintaining all original structural choices
+
+### Example 5: Update with Historical Context
+
+**User provides:** "Update the Backend Team report with today's updates" + new information
+
+**Assistant should:**
+
+1. Search for previous Backend Team reports in conversation history or knowledge base
+2. Use historical context to understand team structure, naming conventions
+3. Follow established patterns from previous reports
+4. Generate updated report consistent with team's reporting style
+5. Insert new update block before existing blocks
+
+## Multiple Projects Structure Example
+
+**Correct:**
+
+```markdown
+## Alpha Team
+
+### Dashboard Analytics Project
+#### 01-12-2025
+{summary}
+**On track:**
+...
+
+### Mobile App Redesign
+#### 01-12-2025
+{summary}
+**On track:**
+...
+
+## Beta Team
+
+### Social Login Feature
+#### 01-12-2025
+{summary}
+**On track:**
+...
+```
+
+Note: Each team header (`##`) appears only once, with all their projects grouped under it as subheaders (`###`).

package/skills/prod-roadmap-report/rules/status-report-rules.md

@@ -0,0 +1,44 @@
+# Status Report Rules
+
+This is rules and instructions that you need to follow to give right and accurated answers.
+
+Read `CLAUDE.md` and `.claude/status.memory/` in the working directory. If don't exist, run `/status.memory` first.
+## Core Rules and Principles
+
+- **Never invent information** - Only use explicitly stated data
+- **Never infer critical data** - Dates, deadlines, metrics must be explicit
+- **Focus on quality** - not in speed. I prefer you answer right, instead give me fast bad quality informations. But, don't waste tokens. Be concise if you need, and expand the answer if the user asks for it.
+- **Ask when unclear** - Request clarification for missing critical info
+- **Flexible input** - Accept any format (text, markdown, Google Docs, transcriptions)
+- **Contextual intelligence** - Infer team/project names from context when reasonable
+- **Automatic language detection** - Match user's language for all output and template content. The final content of the templates, need to be the same users language or the language users set.
+- **Historical context awareness** - Use previous reports for consistency, never for inventing data
+- **Update capability** - Update existing reports maintaining exact structure
+- **Fill YAML correctly** - Final output files need to have the yaml filled correctly. Use the existing notes to learn and reference patterns. Don't create others properties, use only the defined in templates
+- **RAG status**: If the user defined the RAG status is the true. If user don't give this information, assume the status based on the latest informations
+## Output Formats
+**Default:** 
+- Markdown (.md)
+- Language following the existing files languages or other language only when the user asks
+### File naming pattern
+- By default, follow the kabeb-case to create the final files.
+- Multiple teams: `all-teams-status-report-{YYYY-MM-DD}.md`
+- Single team day report: `{team_name}-status-report-{YYYY-MM-DD}.md`
+- Single Compiled Team: `{team_name}-compiled-status-report-{YYYY-MM-DD}.md`
+- Ask for team name if unknown
+- If you will save the file to Obsidian Vault, use Title Case com espaços, where the name of the file is the Title of the File.
+
+### When you need to ask something
+Whenever you need to ask specific questions, where the user needs to choose between options, ask strategic and direct questions, if you support `AskUserQuestion` use it when available. If you are Claude or Claude Code, you must use `AskUserQuestion`. Otherwise, use the standard question structure below. Show the questions in formatted table:
+
+```
+|     | {Question you must ask to user. Be objective:} |
+| --- | ------------------------------------------------------------- |
+| A   | {Answer 1}|
+| B   | {Answer 2}|
+| C   | {Answer 3}|
+| D   | {Answer 4}|
+```
+
+## Reference guidance
+For section guidelines, historical context usage, edge cases, and detailed examples, see: `references/detailed-guide.md`

package/skills/prod-roadmap-report/templates/template-multiple-teams-compiled-status.md

@@ -0,0 +1,53 @@
+---
+tags:
+  - work/report
+updated:
+  YYYY-MM-YY:
+type: note
+related:
+  - "[[Name of the file used to build this report without the extension]]"
+  - "[[Name of the file used to build this report without the extension]]"
+---
+
+
+# Status Report Global
+
+This document includes all status reports from teams and your products/projects.
+
+{follow the structure above for each team and your status.}
+
+## {team_name}
+
+### {Project/Initiative/Feature name}
+
+- status: {icebox|planning|scheduled|in progress|late|re-scheduled|done}
+- rag status: {on track|risk-concern | problem}
+
+#### {date_now: DD-MM-YYYY}
+{Write a summary divided into paragraphs about what was discussed regarding this topic during the meeting.}
+
+**On track:**
+- {**Topic Name**: Complete description about the topic that is on track.}
+- {follow this list structure}
+
+**Problems:**
+- {**Problem Name**: Complete description of this problem.}
+- {follow this list structure}
+
+**Risks and Concerns:**
+- {**Risk/Concern Name**: Complete description about the topic that is a risk or concern.}
+- {follow this list structure}
+
+**Actions**:
+- {List actions that were mentioned about this topic during the meeting.}
+
+**Links, assets, references:**
+- {links, assets, references, sources inserted in the user notes}
+
+### Done projects
+
+{Move to here, topics with status resolved or done. Maintain the existing strucuture}
+
+### Other informations
+
+{Insert contents about other individual topics}

package/skills/prod-roadmap-report/templates/template-projects-list.md

@@ -0,0 +1,23 @@
+---
+tags:
+  - work/report
+updated:
+  YYYY-MM-YY:
+type: note
+related:
+  - "[[Name of the file used to build this report without the extension]]"
+  - "[[Name of the file used to build this report without the extension]]"
+---
+
+# Project List Report - {today_date: YYYY-MM-DD}
+
+{Create for each team the block below.}
+## {team_name}
+
+Last update: {today_date: DD-MM-YYYY}
+
+| Project/Iniative                  | Description                                                                                            | Observation                   | Status                                                               | RAG rating                          | Priority                             |
+| --------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------- | -------------------------------------------------------------------- | ----------------------------------- | ------------------------------------ |
+| [Project/Initiative/Feature name](link-to-the-file-compiled-file-if-exists) | {max 280 chars description about the what is this project. If you don't know, ask to the user.} | {one tweet brief description} | {icebox\|planning\|scheduled\|in progress\|late\|re-scheduled\|done} | {on track\|risk-concern \| problem} | {lowest\|low\|medium\|high\|highest} |
+| [Project/Initiative/Feature name](link-to-the-file-compiled-file-if-exists) | {max 280 chars description about the what is this project. If you don't know, ask to the user.} | {one tweet brief description} | {icebox\|planning\|scheduled\|in progress\|late\|re-scheduled\|done} | {on track\|risk-concern \| problem} | {lowest\|low\|medium\|high\|highest} |
+

package/skills/prod-roadmap-report/templates/template-single-team-compiled-status.md

@@ -0,0 +1,60 @@
+---
+tags:
+  - work/report
+updated:
+  YYYY-MM-YY:
+type: note
+---
+
+# {team_name} - Status Report - Compiled - {date_now: YYYY-MM-DD}
+
+This document share informations about work status report from **{team_name}** at **{date_now: DD-MM-YYYY}**, including all status of projects, divided by date.
+
+{fill this table based on the the latest informations we have in this report}
+
+
+| Project/Iniative                  | Description                                                                                            | Observation                   | Status                                                               | RAG rating                          | Priority                             |
+| --------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------- | -------------------------------------------------------------------- | ----------------------------------- | ------------------------------------ |
+| {Project/Initiative/Feature name} | {max 280 chars description about the what is this project. If you don't know, ask to the user.} | {one tweet brief description} | {icebox\|planning\|scheduled\|in progress\|late\|re-scheduled\|done} | {on track\|risk-concern \| problem} | {lowest\|low\|medium\|high\|highest} |
+| {Project/Initiative/Feature name} | {max 280 chars description about the what is this project. If you don't know, ask to the user.} | {one tweet brief description} | {icebox\|planning\|scheduled\|in progress\|late\|re-scheduled\|done} | {on track\|risk-concern \| problem} | {lowest\|low\|medium\|high\|highest} |
+
+
+{follow the structure above for each project/product/initiative discussed or given by user. Try to group status informations inside the project and date sections.}
+
+## {Project/Initiative/Feature name}
+
+- status: {icebox|planning|scheduled|in progress|late|re-scheduled|done}
+- rag status: {on track|risk-concern | problem}
+
+### {date_now: DD-MM-YYYY}
+
+{Write a summary, divided into max 2 paragraphs about what was discussed regarding this topic during the meeting.}
+
+{write a concise, with max 5 bullet points, of the this topic during meeting}
+
+**On track:**
+- {**Topic Name**: Complete description about the topic that is on track.}
+- {follow this list structure}
+
+**Problems:**
+- {**Problem Name**: Complete description of this problem.}
+- {follow this list structure}
+
+**Risks and Concerns:**
+- {**Risk/Concern Name**: Complete description about the topic that is a risk or concern.}
+- {follow this list structure}
+
+**Actions**:
+- {List actions that were mentioned about this topic during the meeting.}
+
+**Links, assets, references:**
+- {links, assets, references, sources inserted in the user notes}
+
+## Done projects
+
+{Move to here, topics with status resolved or done. Maintain the existing strucuture}
+
+
+## Other informations
+
+{Insert contents about other individual topics}

package/skills/prod-roadmap-report/templates/template-single-team-status.md

@@ -0,0 +1,49 @@
+---
+tags:
+  - work/report
+updated:
+  YYYY-MM-YY:
+type: note
+---
+
+# {team_name} - Status Report - {date_now: YYYY-MM-DD}
+
+This document share informations about work status report from {team_name} at {date_now: DD-MM-YYYY}
+
+{follow the structure above for each project/product/initiative discussed or given by user.}
+
+## {Project/Initiative/Feature name}
+
+- status: {icebox|planning|scheduled|in progress|late|re-scheduled|done}
+- rag status: {on track|risk-concern | problem}
+
+{Write a summary, divided into max 2 paragraphs about what was discussed regarding this topic during the meeting.}
+
+{write a concise, with max 5 bullet points, of the this topic during meeting}
+
+**On track:**
+- {**Topic Name**: Complete description about the topic that is on track.}
+- {follow this list structure}
+
+**Problems:**
+- {**Problem Name**: Complete description of this problem.}
+- {follow this list structure}
+
+**Risks and Concerns:**
+- {**Risk/Concern Name**: Complete description about the topic that is a risk or concern.}
+- {follow this list structure}
+
+**Actions**:
+- {List actions that were mentioned about this topic during the meeting.}
+
+**Links, assets, references:**
+- {links, assets, references, sources inserted in the user notes}
+
+## Done
+
+{Move to here, topics with status resolved or done. Maintain the existing strucuture}
+
+
+## Other informations
+
+{Insert contents about other individual topics}

package/skills/prod-specs/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: prod-specs
+description: Ações e fluxos de trabalho para criar, modificar, analisar e atualizar especificações de produto como PRDs, FRDs, Storys, e tarefas de gerenciamento de produtos e projetos.
+argument-hint: "Peça para criar, atualizar ou modificar uma especificação de PRD, FRD ou Story."
+allowed-tools: conversation_search, google_drive_search, google_drive_fetch, slack, figma
+disable-model-invocation: false
+license: AGPL-3.0
+metadata:
+  author: jarvis-team
+  version: "1.0"
+---
+
+# Product Specs
+
+Antes de iniciar:
+- Leia o arquivo de regras invioláveis em `rules/prod-spec-rules.md`.
+
+## Diretórios e Variáveis dessa Skill
+
+Utilize essas variáveis para interpretar corretamente o contexto as instruções dessa skill. Os endereços são relativos ao diretório raiz desse plugin:
+
+**Diretório da skill:** `${CLAUDE_SKILL_DIR}`
+
+- `$SKILL_TEMPLATE_FOLDER`: `${CLAUDE_SKILL_DIR}/templates/`
+- `$SKILL_REFERENCES_FOLDER`: `${CLAUDE_SKILL_DIR}/references/`
+
+
+## Objetivo
+
+Esta é uma habilidade para ajudar gestores e líderes de produto a executarem suas tarefas e entregarem um trabalho de gestão de alta qualidade, facilitando decisões e análises.
+
+## Quando usar
+- Analisar mercado, concorrentes, outros produtos
+- Analisar o próprio produto para fornecer mais insights e identificar lacunas e oportunidades
+- Criar apresentações estratégicas e táticas 
+- Quando o usuário precisar analisar dados, indicadores e métricas de qualquer tipo
+- quando o usuário precisa criar especificações como:
+    - PRD: Documento de Requisitos do Produto
+    - FRD: Documento de requisitos de recursos
+    - Escreva épicos, histórias e tarefas técnicas
+- Planeje, analise e escreva itens como épicos, histórias, tarefas
+- Priorizar roadmaps, backlogs e planejamento de curto, médio e longo prazo
+- Escrever relatórios de status sobre projetos, obras em andamento
+- Compilar, organizar e escrever informações em documentos bem formatados e estruturados que serão compartilhados
+- apoiar e auxiliar o PM ou líder de produto em qualquer outra tarefa que possa ser necessária em sua função como gerente
+
+## Quando invocar
+
+Essa habilidade deve ser invocada quando o usuário pede para **fazer trabalho real com o produto**, como:
+
+- “Criar/aperfeiçoar um PRD/especificação/caso de negócios/1 página”
+- “Transforme esta ideia em um roteiro” / “Roteiro de resultados para X”
+- “Desenhar um plano de descoberta/roteiro de entrevista/plano de experiência”
+- “Definir métricas de sucesso/OKRs/árvore de métricas”
+- “Posicione este produto em relação aos concorrentes”
+- “Projetar um recurso alimentado por IA / agente GenAI / ciclo de vida AI PM”
+- “Executar uma conversa / feedback / 1:1 / negociação difícil”
+- “Planejar uma estratégia de produto/visão/avaliação de oportunidade”
+
+## Instruções e Referências
+
+SEMPRE utilize as instruções na íntegra contidas nessas referências de acordo com o contexto e pedido:
+
+- Crie, modifique ou esclareça um PRD seguindo as instruções em `references/prod.spec.prd.md`
+- Crie, modifique ou esclareça um FRD seguindo as instruções em `references/prod.spec.frd.md`
+- Avalie, clarifique, detalhe e identifique gaps e possíveis melhorias na especificação seguindo as instruções em `references/prod.spec.clarify.md`
+
+Para outras necessidades não especificadas ou que não possuam instruções ou templates, aplique as boas práticas comumente utilizadas pelos Gerentes de Produto no mercado.
+
+Se o usuário solicitar para ver o que pode ser feito com essa habilidade, cite todas as referências disponíveis com uma descrição concisa.
+
+Cenário A: "Criar um PRD para um aplicativo de tarefas" → Fluxo de trabalho completo de perguntas
+Cenário B: "Crie um PRD com base neste documento: [...]" → Fluxo de trabalho de validação  
+Cenário C: "Editar este PRD: [...]" → Fluxo de trabalho de melhoria focado
+
+Esteja atento quando o usuário conversar em linguagem natural, para acionar comandos usando instruções corretas:
+
+## Templates Disponíveis
+
+Os templates ficam na pasta `templates` dessa skill. Elas devem ser usadas para gerar o output final para o usuário. Suas perguntas devem ser baseadas nesses templates para que eles fiquem completos, detalhados e com qualidade.
+
+- [Template para PRD](templates/prod-prd-template.md)
+- [Template para FRD](templates/prod-frd-template.md) 
+- [Template para épicos](templates/prod-epic-template.md) 
+- [Template para itens (história/tarefa/bug)](templates/prod-issue-template.md) 
+
+**Para PRDs:**
+- "criar um PRD sobre..."
+- "novo PRD para..."
+- "editar o PRD..."
+
+**Para problemas (histórias/tarefas/bugs):**
+- "criar uma história sobre..."
+- "nova tarefa para..."
+- "criar um bug..."
+
+**Para épicos:**
+- "crie um épico sobre..."
+- "novo épico para..."
+
+**Para FRDs:**
+- "criar um FRD sobre..."
+- "novo FRD para..."
+
+**Para esclarecimentos:**
+- "esclarecer a especificação..."
+- "esclarecer o PRD..."
+