@brunosps00/dev-workflow 0.4.3 → 0.4.5

package/bin/dev-workflow.js

@@ -2,6 +2,7 @@
 
 const { run } = require('../lib/init');
 const installDeps = require('../lib/install-deps');
+const uninstall = require('../lib/uninstall');
 
 const args = process.argv.slice(2);
 const command = args[0];
@@ -28,6 +29,8 @@ const HELP_TEXT = `
     update         Update managed files (commands, templates, references, scripts, skills, wrappers, MCPs)
                    Preserves: .dw/rules/, .dw/spec/, user data
     install-deps   Install system dependencies (Playwright browsers, MCP servers)
+    uninstall      Remove all managed files (commands, templates, wrappers, skills, MCPs)
+                   Preserves: .dw/rules/, .dw/spec/, .planning/ (user data)
     help           Show this help message
 
   Options:
@@ -41,6 +44,7 @@ const HELP_TEXT = `
     npx dev-workflow init --force          # Overwrite existing files
     npx dev-workflow update --lang=en      # Update all managed files to latest version
     npx dev-workflow install-deps          # Install Playwright browsers and MCP servers
+    npx dev-workflow uninstall             # Remove all managed files (preserves user data)
 `;
 
 async function main() {
@@ -54,6 +58,9 @@ async function main() {
     case 'install-deps':
       installDeps.run();
       break;
+    case 'uninstall':
+      uninstall.run();
+      break;
     case 'help':
     case '--help':
     case '-h':

package/lib/uninstall.js

@@ -0,0 +1,111 @@
+const fs = require('fs');
+const path = require('path');
+const { COMMANDS, PLATFORMS, MCP_SERVERS } = require('./constants');
+
+function run() {
+  const projectRoot = process.cwd();
+
+  console.log('\n  dev-workflow uninstall');
+  console.log(`  ${'='.repeat(40)}\n`);
+
+  let removed = 0;
+  let skipped = 0;
+
+  function removeDir(dirPath, label) {
+    if (fs.existsSync(dirPath)) {
+      fs.rmSync(dirPath, { recursive: true });
+      console.log(`  \x1b[31m-\x1b[0m ${path.relative(projectRoot, dirPath)} [removed]`);
+      removed++;
+    } else {
+      skipped++;
+    }
+  }
+
+  function removeFile(filePath) {
+    if (fs.existsSync(filePath)) {
+      fs.unlinkSync(filePath);
+      console.log(`  \x1b[31m-\x1b[0m ${path.relative(projectRoot, filePath)} [removed]`);
+      removed++;
+    } else {
+      skipped++;
+    }
+  }
+
+  // 1. Remove .dw/commands/, .dw/templates/, .dw/references/, .dw/scripts/
+  console.log('  Managed files:');
+  removeDir(path.join(projectRoot, '.dw', 'commands'), '.dw/commands/');
+  removeDir(path.join(projectRoot, '.dw', 'templates'), '.dw/templates/');
+  removeDir(path.join(projectRoot, '.dw', 'references'), '.dw/references/');
+  removeDir(path.join(projectRoot, '.dw', 'scripts'), '.dw/scripts/');
+  console.log();
+
+  // 2. Remove platform wrappers (only dw-* skills, not user skills)
+  console.log('  Platform wrappers:');
+  const allCommandNames = COMMANDS.en.map(c => c.name);
+
+  for (const [, platform] of Object.entries(PLATFORMS)) {
+    for (const name of allCommandNames) {
+      if (platform.flat) {
+        removeFile(path.join(projectRoot, platform.dir, `${name}.md`));
+      } else {
+        removeDir(path.join(projectRoot, platform.dir, name));
+      }
+    }
+  }
+  console.log();
+
+  // 3. Remove bundled skills from .agents/skills/
+  console.log('  Bundled skills:');
+  const bundledSkills = [
+    'humanizer',
+    'remotion-best-practices',
+    'security-review',
+    'ui-ux-pro-max',
+    'vercel-react-best-practices',
+    'webapp-testing',
+  ];
+  for (const skill of bundledSkills) {
+    removeDir(path.join(projectRoot, '.agents', 'skills', skill));
+  }
+  console.log();
+
+  // 4. Remove MCP servers from .claude/settings.json
+  console.log('  MCP Servers:');
+  const settingsPath = path.join(projectRoot, '.claude', 'settings.json');
+  if (fs.existsSync(settingsPath)) {
+    try {
+      const settings = JSON.parse(fs.readFileSync(settingsPath, 'utf-8'));
+      if (settings.mcpServers) {
+        for (const name of Object.keys(MCP_SERVERS)) {
+          if (settings.mcpServers[name]) {
+            delete settings.mcpServers[name];
+            console.log(`  \x1b[31m-\x1b[0m MCP server: ${name} [removed]`);
+            removed++;
+          }
+        }
+        fs.writeFileSync(settingsPath, JSON.stringify(settings, null, 2) + '\n', 'utf-8');
+      }
+    } catch {
+      console.log('    Could not parse .claude/settings.json, skipping MCP cleanup');
+    }
+  }
+  console.log();
+
+  // 5. Remove .opencode/package.json
+  removeFile(path.join(projectRoot, '.opencode', 'package.json'));
+
+  // 6. Remove legacy .codex/skills/
+  removeDir(path.join(projectRoot, '.codex', 'skills'));
+
+  // Note: .dw/rules/, .dw/spec/, .planning/ are USER DATA — never removed
+  console.log(`\n  ${'='.repeat(40)}`);
+  console.log(`  Done! ${removed} removed, ${skipped} already absent`);
+  console.log();
+  console.log('  Preserved (user data):');
+  console.log('    .dw/rules/    (project rules)');
+  console.log('    .dw/spec/     (PRDs and specs)');
+  console.log('    .planning/    (GSD state)');
+  console.log();
+}
+
+module.exports = { run };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brunosps00/dev-workflow",
-  "version": "0.4.3",
+  "version": "0.4.5",
   "description": "AI-driven development workflow commands for any project. Scaffolds a complete PRD-to-PR pipeline with multi-platform AI assistant support.",
   "bin": {
     "dev-workflow": "./bin/dev-workflow.js"

package/scaffold/en/commands/dw-autopilot.md

@@ -53,6 +53,7 @@ If this command is invoked to resume an interrupted autopilot (via `/dw-resume`)
 Evaluate whether the topic requires deep research:
 - **YES** (run `/dw-deep-research`): new technology for the project, unknown domain, external API integrations, critical architectural decisions
 - **NO** (skip to step 3): simple feature in an already mapped domain, refactoring existing code, basic CRUD
+  - If skipping, DOCUMENT the reason in the progress block. E.g.: "Research skipped — domain already mapped in .dw/rules/[file].md". The user must see the justification.
 
 If executed, use `standard` mode by default. Incorporate findings into subsequent steps.
 
@@ -60,8 +61,8 @@ If executed, use `standard` mode by default. Incorporate findings into subsequen
 
 Run `/dw-brainstorm` with accumulated context (intel + research).
 - Generate 3 directions
-- Automatically converge on the most pragmatic option for the project context
-- Do NOT wait for user approval (brainstorm is automatic in autopilot)
+- Present the 3 directions to the user with your recommendation highlighted and justified
+- Wait for user confirmation on which direction to follow before proceeding
 
 ### Step 4: PRD (Interactive — 7+ Questions)
 
@@ -72,6 +73,7 @@ Run `/dw-create-prd` using brainstorm findings.
 - Ask at least 7 questions about: problem, target users, critical features, scope, constraints, design, integration
 - In each question, present a recommendation grounded in brainstorm and deep-research findings (if executed). E.g.: "Based on the research, I recommend X because [evidence]. Do you agree or prefer a different direction?"
 - Wait for user responses to each question
+- This step is BLOCKING — the command STOPS until a response is received from the user for EACH question. If the user does not respond, do NOT proceed. Do NOT assume answers based on context.
 - Only after receiving all responses, write the complete PRD in `.dw/spec/prd-[name]/prd.md`
 
 ### === GATE 1: PRD Approval ===
@@ -92,6 +94,7 @@ Run `/dw-create-techspec` from the approved PRD.
 - Ask at least 7 questions about: preferred architecture, existing vs new libs, testing strategy, integration with existing systems, infrastructure constraints, performance, security
 - In each question, present a technical recommendation grounded in brainstorm, deep-research, and approved PRD findings. E.g.: "Research indicated lib X has better performance for this case [source]. Want to use X or have another preference?"
 - Wait for user responses to each question
+- This step is BLOCKING — the command STOPS until a response is received from the user for EACH question. If the user does not respond, do NOT proceed. Do NOT assume answers based on context.
 - Only after receiving all responses, generate in `.dw/spec/prd-[name]/techspec.md`
 
 ### Step 6: Tasks
@@ -114,7 +117,7 @@ Present to the user:
 Evaluate whether tasks involve frontend:
 - **YES** (run `/dw-redesign-ui`): if there are tasks with visual components AND the `ui-ux-pro-max` skill is available
   - Generate the design contract in `.dw/spec/prd-[name]/design-contract.md`
-  - Do NOT wait for approval (contract is automatic in autopilot, based on PRD requirements)
+  - Present a summary of the design contract to the user (palette, typography, mobile/desktop layout) as a visual checkpoint before proceeding
 - **NO** (skip to step 8): purely backend/infra tasks
 
 ### Step 8: Execution
@@ -150,7 +153,7 @@ Run `/dw-run-qa` with Playwright MCP.
 
 If QA found bugs:
 - Run `/dw-fix-qa` to fix and retest
-- Loop until stable
+- Loop until stable (maximum 5 cycles). After 5 cycles, STOP and ask the user how to proceed.
 
 ### Step 12: Implementation Review (Post-QA)
 
@@ -219,6 +222,8 @@ Save the file `.dw/spec/prd-[name]/autopilot-state.json` with the following form
 - If the session drops, `/dw-resume` will read this file and continue from the correct step
 - When the pipeline finishes (after commit or PR), remove the file or mark `"status": "completed"`
 
+<critical>After EACH completed step, display the updated progress block to the user. This is MANDATORY — the user MUST see what was done and what comes next. If a step was skipped, the reason MUST appear in the progress block.</critical>
+
 ## Progress Format
 
 During execution, report progress in this format:

package/scaffold/pt-br/commands/dw-autopilot.md

@@ -53,6 +53,7 @@ Se este comando for invocado para retomar um autopilot interrompido (via `/dw-re
 Avalie se o topico necessita de pesquisa profunda:
 - **SIM** (execute `/dw-deep-research`): tecnologia nova para o projeto, dominio desconhecido, integracoes com APIs externas, decisoes arquiteturais criticas
 - **NAO** (pule para etapa 3): feature simples no dominio ja mapeado, refatoracao de algo existente, CRUD basico
+  - Se pular, DOCUMENTE o motivo no bloco de progresso. Ex: "Pesquisa pulada — dominio ja mapeado em .dw/rules/[arquivo].md". O usuario deve ver a justificativa.
 
 Se executar, use modo `standard` por padrao. Incorpore os findings nas etapas seguintes.
 
@@ -60,8 +61,8 @@ Se executar, use modo `standard` por padrao. Incorpore os findings nas etapas se
 
 Execute `/dw-brainstorm` com o contexto acumulado (intel + pesquisa).
 - Gere 3 direcoes
-- Convirja automaticamente na opcao mais pragmatica para o contexto do projeto
-- NAO aguarde aprovacao do usuario (brainstorm e automatico no autopilot)
+- Apresente as 3 direcoes ao usuario com sua recomendacao destacada e justificativa
+- Aguarde confirmacao do usuario sobre qual direcao seguir antes de prosseguir
 
 ### Etapa 4: PRD (Interativo — 7+ Perguntas)
 
@@ -72,6 +73,7 @@ Execute `/dw-create-prd` usando os findings do brainstorm.
 - Faca pelo menos 7 perguntas ao usuario sobre: problema, usuarios-alvo, funcionalidades criticas, escopo, restricoes, design, integracao
 - Em cada pergunta, apresente uma recomendacao embasada nos findings do brainstorm e do deep-research (se executado). Ex: "Com base na pesquisa, recomendo X porque [evidencia]. Concorda ou prefere outra direcao?"
 - Aguarde as respostas do usuario para cada pergunta
+- Este passo e BLOQUEANTE — o comando PARA ate receber resposta do usuario para CADA pergunta. Se o usuario nao responder, NAO prossiga. NAO assuma respostas com base no contexto.
 - So apos receber todas as respostas, redija o PRD completo em `.dw/spec/prd-[nome]/prd.md`
 
 ### ═══ GATE 1: Aprovacao do PRD ═══
@@ -92,6 +94,7 @@ Execute `/dw-create-techspec` a partir do PRD aprovado.
 - Faca pelo menos 7 perguntas ao usuario sobre: arquitetura preferida, libs existentes vs novas, estrategia de testes, integracao com sistemas existentes, restricoes de infraestrutura, performance, seguranca
 - Em cada pergunta, apresente uma recomendacao tecnica embasada nos findings do brainstorm, deep-research e PRD aprovado. Ex: "A pesquisa indicou que a lib X tem melhor performance para este caso [fonte]. Quer usar X ou tem outra preferencia?"
 - Aguarde as respostas do usuario para cada pergunta
+- Este passo e BLOQUEANTE — o comando PARA ate receber resposta do usuario para CADA pergunta. Se o usuario nao responder, NAO prossiga. NAO assuma respostas com base no contexto.
 - So apos receber todas as respostas, gere em `.dw/spec/prd-[nome]/techspec.md`
 
 ### Etapa 6: Tasks
@@ -114,7 +117,7 @@ Apresente ao usuario:
 Avalie se as tasks envolvem frontend:
 - **SIM** (execute `/dw-redesign-ui`): se houver tasks com componentes visuais E a skill `ui-ux-pro-max` estiver disponivel
   - Gere o design contract em `.dw/spec/prd-[nome]/design-contract.md`
-  - NAO aguarde aprovacao (o contract e automatico no autopilot, baseado nos requisitos do PRD)
+  - Apresente um resumo do design contract ao usuario (paleta, tipografia, layout mobile/desktop) como checkpoint visual antes de prosseguir
 - **NAO** (pule para etapa 8): tasks puramente backend/infra
 
 ### Etapa 8: Execucao
@@ -150,7 +153,7 @@ Execute `/dw-run-qa` com Playwright MCP.
 
 Se o QA encontrou bugs:
 - Execute `/dw-fix-qa` para corrigir e retestar
-- Loop ate estabilizar
+- Loop ate estabilizar (maximo 5 ciclos). Apos 5 ciclos, PARE e pergunte ao usuario como deseja prosseguir.
 
 ### Etapa 12: Review de Implementacao (Pos-QA)
 
@@ -219,6 +222,8 @@ Salve o arquivo `.dw/spec/prd-[nome]/autopilot-state.json` com o seguinte format
 - Se a sessao cair, o `/dw-resume` lera este arquivo e continuara da etapa correta
 - Ao finalizar o pipeline (apos commit ou PR), remova o arquivo ou marque `"status": "completed"`
 
+<critical>Apos CADA etapa completada, exiba o bloco de progresso atualizado ao usuario. Isso e OBRIGATORIO — o usuario DEVE ver o que foi feito e o que vem a seguir. Se uma etapa foi pulada, o motivo DEVE aparecer no bloco de progresso.</critical>
+
 ## Formato de Progresso
 
 Durante a execucao, reporte progresso no formato: