workflow-agent-cli 2.1.0 → 2.2.0

package/templates/LIBRARY_INVENTORY.md

@@ -84,13 +84,13 @@
 
 ```typescript
 // Browser client (singleton)
-import { getSupabaseClient } from '@/lib/supabase/client';
+import { getSupabaseClient } from "@/lib/supabase/client";
 
 // Server client (for server components/actions)
-import { createServerClient } from '@/lib/supabase/server';
+import { createServerClient } from "@/lib/supabase/server";
 
 // Admin client (bypasses RLS)
-import { createAdminClient } from '@/lib/supabase/admin';
+import { createAdminClient } from "@/lib/supabase/admin";
 ```
 
 **Files:**
@@ -112,11 +112,11 @@ import { createAdminClient } from '@/lib/supabase/admin';
 **Usage Patterns:**
 
 ```typescript
-import { useQuery, useMutation, useQueryClient } from '@tanstack/react-query';
+import { useQuery, useMutation, useQueryClient } from "@tanstack/react-query";
 
 // Fetching data
 const { data, isLoading, error } = useQuery({
-  queryKey: ['tasks', boardId],
+  queryKey: ["tasks", boardId],
   queryFn: () => getTasks(boardId),
 });
 
@@ -125,7 +125,7 @@ const queryClient = useQueryClient();
 const mutation = useMutation({
   mutationFn: createTask,
   onSuccess: () => {
-    queryClient.invalidateQueries({ queryKey: ['tasks'] });
+    queryClient.invalidateQueries({ queryKey: ["tasks"] });
   },
 });
 ```
@@ -197,9 +197,9 @@ const mutation = useMutation({
 **Usage Pattern:**
 
 ```typescript
-import { Button } from '@/components/ui/button';
-import { Dialog, DialogContent, DialogHeader } from '@/components/ui/dialog';
-import { Input } from '@/components/ui/input';
+import { Button } from "@/components/ui/button";
+import { Dialog, DialogContent, DialogHeader } from "@/components/ui/dialog";
+import { Input } from "@/components/ui/input";
 ```
 
 ### Lucide React (Icons)
@@ -234,11 +234,11 @@ import { Plus, Trash, Settings, ChevronDown } from "lucide-react";
 **Usage Pattern:**
 
 ```typescript
-import { toast } from 'sonner';
+import { toast } from "sonner";
 
-toast.success('Task created successfully');
-toast.error('Failed to delete task');
-toast.loading('Saving changes...');
+toast.success("Task created successfully");
+toast.error("Failed to delete task");
+toast.loading("Saving changes...");
 ```
 
 ### Vaul (Drawer)
@@ -273,12 +273,12 @@ toast.loading('Saving changes...');
 **Usage Pattern:**
 
 ```typescript
-import { useForm } from 'react-hook-form';
-import { zodResolver } from '@hookform/resolvers/zod';
+import { useForm } from "react-hook-form";
+import { zodResolver } from "@hookform/resolvers/zod";
 
 const form = useForm<FormData>({
   resolver: zodResolver(formSchema),
-  defaultValues: { title: '', description: '' },
+  defaultValues: { title: "", description: "" },
 });
 ```
 
@@ -294,13 +294,13 @@ const form = useForm<FormData>({
 **Usage Patterns:**
 
 ```typescript
-import { z } from 'zod';
+import { z } from "zod";
 
 // Define schema
 export const TaskSchema = z.object({
   id: z.string().uuid(),
   title: z.string().min(1).max(255),
-  priority: z.enum(['low', 'medium', 'high', 'critical']),
+  priority: z.enum(["low", "medium", "high", "critical"]),
 });
 
 // Infer type from schema
@@ -520,9 +520,9 @@ pnpm test:e2e  # Run E2E tests
 **Usage Pattern:**
 
 ```typescript
-import { format, parseISO, differenceInDays } from 'date-fns';
+import { format, parseISO, differenceInDays } from "date-fns";
 
-format(new Date(), 'MMM d, yyyy'); // "Jan 8, 2026"
+format(new Date(), "MMM d, yyyy"); // "Jan 8, 2026"
 differenceInDays(endDate, startDate);
 ```
 

package/templates/SCOPE_CREATION_WORKFLOW.md

@@ -5,6 +5,7 @@ This document provides a structured workflow for AI agents creating custom scope
 ## Critical Rule: Zero-Assumption Principle
 
 **Never assume or infer details about:**
+
 - Project domain or industry
 - Feature areas or scope names
 - Naming conventions
@@ -20,6 +21,7 @@ This document provides a structured workflow for AI agents creating custom scope
 ### 1. Project Domain Clarification
 
 **Prompt:**
+
 > "What is the primary domain or industry for this project? For example: fintech, healthcare, gaming, education, e-commerce, etc."
 
 **Purpose:** Understand the context to suggest relevant scope categories.
@@ -31,6 +33,7 @@ This document provides a structured workflow for AI agents creating custom scope
 ### 2. Feature Area Enumeration
 
 **Prompt:**
+
 > "What are the main feature areas or functional components of your project? Please list them (aim for 8-15 areas). For example, for a SaaS app: authentication, user profiles, billing, notifications, analytics."
 
 **Purpose:** Identify specific scopes that map to actual functionality.
@@ -38,6 +41,7 @@ This document provides a structured workflow for AI agents creating custom scope
 **Expected Response:** List of feature areas (comma-separated or numbered).
 
 **Follow-up:** If fewer than 8 or more than 20 features listed:
+
 > "You listed [N] features. The recommended range is 8-15 scopes. Would you like to add more detail, consolidate some areas, or proceed as is?"
 
 ---
@@ -45,11 +49,13 @@ This document provides a structured workflow for AI agents creating custom scope
 ### 3. Naming Convention Preferences
 
 **Prompt:**
+
 > "What naming style do you prefer for your scopes? Examples:
+>
 > - Single words (auth, billing, users)
 > - Kebab-case (user-management, api-endpoints)
 > - Descriptive phrases (subscription-billing, email-notifications)
-> 
+>
 > Note: All scope names must be lowercase alphanumeric with hyphens only."
 
 **Purpose:** Ensure consistent naming that matches team conventions.
@@ -61,11 +67,13 @@ This document provides a structured workflow for AI agents creating custom scope
 ### 4. Scope-to-Structure Mapping
 
 **Prompt:**
+
 > "Do your scopes map to:
+>
 > 1. **Folders/modules** in your codebase (e.g., src/auth, src/billing)
 > 2. **Feature areas** regardless of folder structure
 > 3. **Both** - they align with both features and folders
-> 
+>
 > This helps determine how granular the scopes should be."
 
 **Purpose:** Align scopes with actual codebase organization.
@@ -77,10 +85,12 @@ This document provides a structured workflow for AI agents creating custom scope
 ### 5. Migration vs. New Creation
 
 **Prompt:**
+
 > "Are you:
+>
 > 1. **Migrating** existing scopes from workflow.config.json to a package
 > 2. **Creating** a new custom scope package from scratch
-> 
+>
 > If migrating, I can use your existing scope definitions. If creating new, we'll define them together."
 
 **Purpose:** Determine whether to use existing data or start fresh.
@@ -88,9 +98,10 @@ This document provides a structured workflow for AI agents creating custom scope
 **Expected Response:** "migrate" or "create new"
 
 **Follow-up if "migrate":**
+
 > "I found [N] scopes in your workflow.config.json:
 > [List scopes]
-> 
+>
 > Should I use these as-is, or would you like to review/modify them first?"
 
 ---
@@ -98,11 +109,13 @@ This document provides a structured workflow for AI agents creating custom scope
 ### 6. Package Publishing Intent
 
 **Prompt:**
+
 > "Do you plan to:
+>
 > 1. **Publish** this scope package to npm for reuse across projects
 > 2. **Keep it local** to this workspace only
 > 3. **Undecided** - create it now, decide later
-> 
+>
 > This affects whether we include publishing configuration."
 
 **Purpose:** Include appropriate publishing metadata and instructions.
@@ -130,22 +143,27 @@ Before generating the package, confirm:
 For each scope, ask:
 
 **Prompt:**
+
 > "Scope #[N] - Name: (lowercase, alphanumeric, hyphens only)"
 
 After name is provided:
 
 **Prompt:**
+
 > "Description for '[scope-name]': (minimum 10 characters, be specific)"
 
 After description:
 
 **Prompt:**
+
 > "Emoji for '[scope-name]': (optional, press Enter to skip)"
 
 After emoji:
 
 **Prompt:**
+
 > "Category for '[scope-name]':
+>
 > 1. auth - Authentication & Authorization
 > 2. features - Features & Functionality
 > 3. infrastructure - Infrastructure & DevOps
@@ -154,14 +172,15 @@ After emoji:
 > 6. performance - Performance & Optimization
 > 7. other - Other
 > 8. (none) - No category
-> 
+>
 > Choose 1-8:"
 
 After each scope:
 
 **Prompt:**
+
 > "✓ Added scope: [scope-name]
-> 
+>
 > You have [N] scopes. Add another? (y/n)"
 
 ---
@@ -172,9 +191,9 @@ After each scope:
 Agent: What is the primary domain or industry for this project?
 User: Healthcare SaaS platform
 
-Agent: What are the main feature areas of your healthcare SaaS? 
+Agent: What are the main feature areas of your healthcare SaaS?
       (aim for 8-15 areas)
-User: patient records, appointments, billing, insurance, 
+User: patient records, appointments, billing, insurance,
       prescriptions, lab results, messaging, reports
 
 Agent: What naming style do you prefer?
@@ -215,18 +234,22 @@ User: y
 If user provides invalid input:
 
 **For invalid scope name:**
+
 > "The name '[name]' is invalid. Scope names must be:
+>
 > - Lowercase letters, numbers, and hyphens only
 > - Maximum 32 characters
 > - Not a reserved word (init, create, build, test, config, docs, ci, deps)
-> 
+>
 > Please provide a different name:"
 
 **For short description:**
-> "The description must be at least 10 characters to be meaningful. 
+
+> "The description must be at least 10 characters to be meaningful.
 > Please provide more detail about what '[scope-name]' covers:"
 
 **For duplicate name:**
+
 > "A scope named '[name]' already exists. Please choose a different name:"
 
 ---
@@ -236,10 +259,13 @@ If user provides invalid input:
 After successfully creating the package, provide:
 
 1. **Location confirmation:**
+
    > "✨ Custom scope package created at: [path]"
 
 2. **Next steps:**
+
    > "Next steps:
+   >
    > 1. cd [path]
    > 2. pnpm install
    > 3. pnpm build
@@ -247,7 +273,9 @@ After successfully creating the package, provide:
    > 5. Update repository URL in package.json"
 
 3. **Publishing instructions** (if user indicated intent):
+
    > "To publish to npm:
+   >
    > 1. npm login
    > 2. Update version in package.json as needed
    > 3. pnpm publish --access public"

package/templates/SELF_IMPROVEMENT_MANDATE.md

@@ -42,6 +42,7 @@ ANY time a developer, AI agent, or team member receives an "ask" or suggestion t
 ### Improvement Suggestion Template
 
 \`\`\`markdown
+
 # Improvement Suggestion
 
 **ID**: <unique-id>
@@ -69,11 +70,13 @@ ANY time a developer, AI agent, or team member receives an "ask" or suggestion t
 ## Implementation Plan
 
 ### Changes Required
+
 - [ ] File/component to modify — `path/to/file.ts`
 - [ ] Update documentation — `docs/section.md`
 - [ ] Add tests — `tests/improvement.test.ts`
 
 ### Testing
+
 - [ ] Unit tests added
 - [ ] Integration tests added
 - [ ] Manual testing completed
@@ -88,7 +91,7 @@ ANY time a developer, AI agent, or team member receives an "ask" or suggestion t
 
 ---
 
-*To submit this improvement to the workflow-agent community:*
+_To submit this improvement to the workflow-agent community:_
 \`\`\`bash
 workflow suggest "$(cat .workflow/improvements/YYYY-MM-DD-<id>.md)"
 \`\`\`
@@ -128,23 +131,24 @@ The workflow system MUST proactively analyze usage patterns and offer suggestion
 <One-line summary of the issue>
 
 Details:
-  • <Specific observation or pattern detected>
-  • <Impact or frequency data>
-  • <Concrete example from git history>
+• <Specific observation or pattern detected>
+• <Impact or frequency data>
+• <Concrete example from git history>
 
 Recommendation:
-  <Actionable suggestion with exact command or config change>
+<Actionable suggestion with exact command or config change>
 
 To apply automatically:
-  workflow apply-suggestion <id>
+workflow apply-suggestion <id>
 
 To provide feedback:
-  workflow suggest "Alternative approach: ..."
+workflow suggest "Alternative approach: ..."
 \`\`\`
 
 ### Pattern Detection Examples
 
 **Example 1: Common Typo**
+
 ```
 💡 Workflow Optimization Suggestion
 
@@ -170,6 +174,7 @@ To apply automatically:
 ```
 
 **Example 2: Scope Consolidation**
+
 ```
 💡 Workflow Optimization Suggestion
 
@@ -211,6 +216,7 @@ ALL implemented improvements MUST be documented in `WORKFLOW_CHANGELOG.md` with:
 ### Changelog Template
 
 \`\`\`markdown
+
 ## {{VERSION}} - {{DATE}}
 
 ### {{CATEGORY}} Improvements
@@ -244,15 +250,15 @@ Edit `workflow.config.ts`:
 
 \`\`\`typescript
 export default {
-  projectName: '{{PROJECT_NAME}}',
-  scopes: [...],
-  
-  // Enable community improvement syncing
-  syncRemote: 'https://workflow-improvements.dev/registry',
-  analytics: {
-    enabled: true,
-    shareAnonymous: true, // Help improve the tool!
-  },
+projectName: '{{PROJECT_NAME}}',
+scopes: [...],
+
+// Enable community improvement syncing
+syncRemote: 'https://workflow-improvements.dev/registry',
+analytics: {
+enabled: true,
+shareAnonymous: true, // Help improve the tool!
+},
 };
 \`\`\`
 
@@ -294,5 +300,5 @@ Every suggestion makes the workflow better for everyone. Your feedback matters!
 
 ---
 
-*Generated by @hawkinside_out/workflow-agent - a self-evolving workflow management system*  
-*Learn more: https://workflow.dev/docs/self-improvement*
+_Generated by @hawkinside_out/workflow-agent - a self-evolving workflow management system_  
+_Learn more: https://workflow.dev/docs/self-improvement_

package/templates/SINGLE_SOURCE_OF_TRUTH.md

@@ -33,20 +33,20 @@ All Supabase client creation MUST go through these files. Never create clients d
 
 ```typescript
 // ❌ WRONG - Never create clients directly
-import { createClient } from '@supabase/supabase-js';
+import { createClient } from "@supabase/supabase-js";
 const supabase = createClient(url, key);
 
 // ✅ CORRECT - Use the appropriate helper
 // In client components:
-import { getSupabaseClient } from '@/lib/supabase/client';
+import { getSupabaseClient } from "@/lib/supabase/client";
 const supabase = getSupabaseClient();
 
 // In server actions/components:
-import { createServerClient } from '@/lib/supabase/server';
+import { createServerClient } from "@/lib/supabase/server";
 const supabase = await createServerClient();
 
 // For admin operations (bypasses RLS):
-import { createAdminClient } from '@/lib/supabase/admin';
+import { createAdminClient } from "@/lib/supabase/admin";
 const supabase = createAdminClient();
 ```
 
@@ -66,27 +66,38 @@ Authorization logic is centralized in these files. Never implement permission ch
 
 ```typescript
 // Role types
-export type OrgRole = 'super_admin' | 'owner' | 'admin' | 'manager' | 'developer' | 'viewer';
+export type OrgRole =
+  | "super_admin"
+  | "owner"
+  | "admin"
+  | "manager"
+  | "developer"
+  | "viewer";
 
 // Role hierarchy (higher index = more permissions)
 export const ROLE_HIERARCHY: OrgRole[] = [
-  'viewer',
-  'developer',
-  'manager',
-  'admin',
-  'owner',
-  'super_admin',
+  "viewer",
+  "developer",
+  "manager",
+  "admin",
+  "owner",
+  "super_admin",
 ];
 
 // Role groups for permission checks
-export const ADMIN_ROLES: OrgRole[] = ['super_admin', 'owner', 'admin'];
-export const PRIVILEGED_ROLES: OrgRole[] = ['super_admin', 'owner', 'admin', 'manager'];
+export const ADMIN_ROLES: OrgRole[] = ["super_admin", "owner", "admin"];
+export const PRIVILEGED_ROLES: OrgRole[] = [
+  "super_admin",
+  "owner",
+  "admin",
+  "manager",
+];
 export const CONTRIBUTOR_ROLES: OrgRole[] = [
-  'super_admin',
-  'owner',
-  'admin',
-  'manager',
-  'developer',
+  "super_admin",
+  "owner",
+  "admin",
+  "manager",
+  "developer",
 ];
 ```
 
@@ -100,13 +111,13 @@ import {
   requireAdminAccess,
   requirePrivilegedAccess,
   requireContributorAccess,
-} from '@/utils/authorization.server';
+} from "@/utils/authorization.server";
 
 // In server actions - always verify access FIRST
 export async function getTask(taskId: string) {
   const access = await verifyTaskAccess(taskId);
   if (!access.hasAccess) {
-    return { data: null, error: access.error || 'Access denied' };
+    return { data: null, error: access.error || "Access denied" };
   }
   // ... proceed with data access
 }
@@ -179,19 +190,19 @@ export type TaskType = "story" | "task" | "bug" | "epic";
 
 ```typescript
 // lib/validations/task.schema.ts
-import { z } from 'zod';
+import { z } from "zod";
 
 export const TaskSchema = z.object({
   id: z.string().uuid(),
   ticketId: z.string().regex(/^[A-Z]{1,6}-\d{4}$/),
   title: z.string().min(1).max(255),
-  priority: z.enum(['low', 'medium', 'high', 'critical']),
+  priority: z.enum(["low", "medium", "high", "critical"]),
 });
 
 export type Task = z.infer<typeof TaskSchema>;
 
 // lib/validations/index.ts
-export { TaskSchema, type Task } from './task.schema';
+export { TaskSchema, type Task } from "./task.schema";
 ```
 
 ---
@@ -233,7 +244,7 @@ app/providers/
 
 ```typescript
 // Always import hooks from the providers module
-import { useAuth, useOrganization, useNotifications } from '@/app/providers';
+import { useAuth, useOrganization, useNotifications } from "@/app/providers";
 
 function MyComponent() {
   const { user, loading } = useAuth();
@@ -277,11 +288,11 @@ Every action file MUST:
 4. Transform snake_case DB fields to camelCase
 
 ```typescript
-'use server';
+"use server";
 
-import { createServerClient } from '@/lib/supabase/server';
-import { verifyBoardAccess } from '@/utils/authorization.server';
-import { revalidatePath } from 'next/cache';
+import { createServerClient } from "@/lib/supabase/server";
+import { verifyBoardAccess } from "@/utils/authorization.server";
+import { revalidatePath } from "next/cache";
 
 export async function getTasks(boardId: string) {
   const access = await verifyBoardAccess(boardId);
@@ -290,7 +301,10 @@ export async function getTasks(boardId: string) {
   }
 
   const supabase = await createServerClient();
-  const { data, error } = await supabase.from('tasks').select('*').eq('board_id', boardId);
+  const { data, error } = await supabase
+    .from("tasks")
+    .select("*")
+    .eq("board_id", boardId);
 
   if (error) return { data: null, error: error.message };
 
@@ -317,7 +331,7 @@ Custom React hooks live in `hooks/`.
 ### Hook Pattern
 
 ```typescript
-import { useState, useEffect, useCallback } from 'react';
+import { useState, useEffect, useCallback } from "react";
 
 export function useHookName(param: string) {
   const [data, setData] = useState<DataType | null>(null);
@@ -457,30 +471,33 @@ export function useHookName(param: string) {
 
 ```typescript
 // Supabase clients
-import { getSupabaseClient } from '@/lib/supabase/client';
-import { createServerClient } from '@/lib/supabase/server';
-import { createAdminClient } from '@/lib/supabase/admin';
+import { getSupabaseClient } from "@/lib/supabase/client";
+import { createServerClient } from "@/lib/supabase/server";
+import { createAdminClient } from "@/lib/supabase/admin";
 
 // Authorization
-import { ROLE_HIERARCHY, ADMIN_ROLES } from '@/utils/authorization';
-import { verifyBoardAccess, requireAdminAccess } from '@/utils/authorization.server';
-import { useAuthorization } from '@/hooks/useAuthorization';
+import { ROLE_HIERARCHY, ADMIN_ROLES } from "@/utils/authorization";
+import {
+  verifyBoardAccess,
+  requireAdminAccess,
+} from "@/utils/authorization.server";
+import { useAuthorization } from "@/hooks/useAuthorization";
 
 // Types
-import type { Task, Board, Sprint, Organization } from '@/types';
-import type { Database } from '@/types/supabase';
+import type { Task, Board, Sprint, Organization } from "@/types";
+import type { Database } from "@/types/supabase";
 
 // Providers/Context
-import { useAuth, useOrganization, useTeams } from '@/app/providers';
+import { useAuth, useOrganization, useTeams } from "@/app/providers";
 
 // UI Components
-import { Button, Input, Dialog } from '@/components/ui';
+import { Button, Input, Dialog } from "@/components/ui";
 
 // Schemas
-import { TaskSchema, CreateTaskSchema } from '@/lib/validations';
+import { TaskSchema, CreateTaskSchema } from "@/lib/validations";
 
 // Test utilities
-import { mockTasks, createMockTask, seedTasks } from '@test/fixtures';
+import { mockTasks, createMockTask, seedTasks } from "@test/fixtures";
 ```
 
 ---