@sppg2001/atomize 2.0.0-alpha.0 → 2.0.1

package/examples/conditional-percentage-template.yaml

@@ -1,167 +0,0 @@
-version: "1.0"
-name: "Story-Aware Task Allocation"
-description: >
-  Demonstrates estimationPercentCondition — each task's weight adapts to
-  the story's size and tags. When the conditional frontend-impl task is
-  skipped, the remaining tasks carry their already-resolved conditional
-  percents into normalization, so the final split is always accurate.
-author: "Atomize"
-tags: ["demo", "conditional-percent", "adaptive"]
-
-filter:
-  workItemTypes:
-    - "User Story"
-  excludeIfHasTasks: true
-
-estimation:
-  strategy: "percentage"
-  rounding: "nearest"
-  minimumTaskPoints: 0.5
-
-tasks:
-  # ── Design ────────────────────────────────────────────────────────────────
-  # Allocation scales with story size.
-  # Small stories (< 5 pts):  10 %  — quick design, no surprises expected
-  # Medium stories (5–12 pts): 15 %  — moderate up-front work
-  # Large stories (≥ 13 pts):  20 %  — epic-scale requires thorough design
-  - id: "design"
-    title: "Technical Design & Architecture"
-    description: "Define architecture, API contracts, and data models for ${story.title}"
-    activity: "Design"
-    assignTo: "@ParentAssignee"
-    estimationPercent: 10
-    estimationPercentCondition:
-      - condition:
-          field: estimation
-          operator: gte
-          value: 13
-        percent: 20
-      - condition:
-          field: estimation
-          operator: gte
-          value: 5
-        percent: 15
-    tags: ["design"]
-
-  # ── Backend implementation ─────────────────────────────────────────────────
-  # Rules evaluated in order — first match wins.
-  #
-  # • fullstack tag present  → 40 %  (budget shared with the frontend task)
-  # • medium/large story     → 50 %  (more surface area to cover carefully)
-  # • fallback               → 60 %  (small, pure-backend story)
-  - id: "backend-impl"
-    title: "Backend Implementation"
-    description: "Implement API endpoints and business logic for ${story.title}"
-    activity: "Development"
-    assignTo: "@ParentAssignee"
-    dependsOn: ["design"]
-    estimationPercent: 60
-    estimationPercentCondition:
-      - condition:
-          field: tags
-          operator: contains
-          value: fullstack
-        percent: 40
-      - condition:
-          field: estimation
-          operator: gte
-          value: 5
-        percent: 50
-    tags: ["backend"]
-
-  # ── Frontend implementation (conditional task) ─────────────────────────────
-  # Only created when the story is tagged "fullstack".
-  # When this task is SKIPPED, the remaining tasks' resolved conditional
-  # percents are used as the baseline for normalization — so Design and
-  # Backend get accurate relative weights rather than stale static values.
-  #
-  # complex-ui tag → extra allocation for non-trivial UIs
-  - id: "frontend-impl"
-    title: "Frontend Implementation"
-    description: "Build UI components and integrate with the API for ${story.title}"
-    activity: "Development"
-    assignTo: "@ParentAssignee"
-    dependsOn: ["design"]
-    condition:
-      field: tags
-      operator: contains
-      value: fullstack
-    estimationPercent: 30
-    estimationPercentCondition:
-      - condition:
-          field: tags
-          operator: contains
-          value: complex-ui
-        percent: 40
-    tags: ["frontend"]
-
-  # ── Testing & QA ──────────────────────────────────────────────────────────
-  # Critical stories need more thorough test coverage.
-  # AND-condition is checked first: critical + large ≥ 8 pts → 30 %
-  # If only critical (smaller story)                        → 25 %
-  # Otherwise                                               → 20 %
-  - id: "testing"
-    title: "Testing & QA"
-    description: "Write automated tests and perform QA for ${story.title}"
-    activity: "Testing"
-    assignTo: "@ParentAssignee"
-    dependsOn: ["backend-impl"]
-    estimationPercent: 20
-    estimationPercentCondition:
-      - condition:
-          all:
-            - field: tags
-              operator: contains
-              value: critical
-            - field: estimation
-              operator: gte
-              value: 8
-        percent: 30
-      - condition:
-          field: tags
-          operator: contains
-          value: critical
-        percent: 25
-    tags: ["testing"]
-
-  # ── Code review ────────────────────────────────────────────────────────────
-  # Always 5 % — lightweight overhead regardless of story size or tags.
-  # No estimationPercentCondition needed here.
-  - id: "code-review"
-    title: "Code Review & Documentation"
-    description: "Peer review and document all changes for ${story.title}"
-    activity: "Documentation"
-    assignTo: "@ParentAssignee"
-    dependsOn: ["testing"]
-    estimationPercent: 5
-    tags: ["review", "documentation"]
-
-# ── Metadata ─────────────────────────────────────────────────────────────────
-metadata:
-  category: "Demo"
-  difficulty: "intermediate"
-  recommendedFor:
-    - "Demonstrating estimationPercentCondition"
-    - "Adaptive task weighting by story size or tags"
-  estimationGuidelines: |
-    Effective resolved percentages by scenario (before normalization):
-
-    Scenario A — small backend-only story (< 5 pts, no "fullstack" tag):
-      design=10  backend=60  testing=20  review=5  → total=95 → normalised to 100
-    Scenario B — medium backend-only story (5/12 pts):
-      design=15  backend=50  testing=20  review=5  → total=90 → normalised to 100
-    Scenario C — medium fullstack story (5/12 pts, "fullstack" tag):
-      design=15  backend=40  frontend=30  testing=20  review=5  → total=110 → normalised
-    Scenario D — large critical fullstack story (≥ 13 pts, "critical" + "fullstack" tags):
-      design=20  backend=40  frontend=30  testing=30  review=5  → total=125 → normalised
-    Scenario E — medium critical backend-only story (5/12 pts, "critical", no "fullstack"):
-      design=15  backend=50  testing=25  review=5  → total=95 → normalised to 100
-
-    Key behaviour: when frontend-impl is skipped (no "fullstack" tag) the
-    remaining tasks already hold their *resolved* conditional percents before
-    normalization runs, so the final ratio reflects the per-story adjustments
-    rather than the static fallback values.
-  examples:
-    - "Small pure-backend story (2 pts, tags: [backend])"
-    - "Medium fullstack story (8 pts, tags: [fullstack])"
-    - "Large critical fullstack story (13 pts, tags: [fullstack, critical, complex-ui])"

package/examples/frontend.yaml

@@ -1,123 +0,0 @@
-version: "1.0"
-name: "Frontend React Feature"
-description: "Standard tasks for React component development"
-author: "Atomize"
-tags: ["frontend", "react", "ui"]
-
-filter:
-  workItemTypes:
-    - "User Story"
-  states:
-    - "New"
-    - "Approved"
-  tags:
-    include:
-      - "frontend"
-      - "react"
-  excludeIfHasTasks: true
-
-tasks:
-  - id: "ui-design-review"
-    title: " UI/UX Design Review"
-    description: |
-      Review designs and create implementation plan:
-      - Review Figma/design specs
-      - Identify reusable components
-      - Plan component hierarchy
-      - Clarify interactions and states
-    estimationPercent: 10
-    tags: ["design", "planning"]
-    activity: "Design"
-
-  - id: "component-structure"
-    title: "Component Structure & Setup"
-    description: |
-      Set up component architecture:
-      - Create component files
-      - Define props interfaces
-      - Set up state management
-      - Configure routing (if needed)
-    estimationPercent: 15
-    tags: ["setup", "architecture"]
-    activity: "Development"
-
-  - id: "component-logic"
-    title: "Component Logic Implementation"
-    description: |
-      Implement core functionality:
-      - Business logic
-      - Event handlers
-      - API integration
-      - Form validation
-    estimationPercent: 30
-    tags: ["implementation", "logic"]
-    activity: "Development"
-    dependsOn:
-      - "component-structure"
-
-  - id: "styling"
-    title: "Styling & Responsive Design"
-    description: |
-      Apply styles and ensure responsiveness:
-      - CSS/Tailwind implementation
-      - Mobile responsiveness
-      - Theme integration
-      - Dark mode (if applicable)
-    estimationPercent: 20
-    tags: ["styling", "css", "responsive"]
-    activity: "Development"
-
-  - id: "accessibility"
-    title: "Accessibility Testing"
-    description: |
-      Ensure WCAG 2.1 AA compliance:
-      - Keyboard navigation
-      - Screen reader testing
-      - ARIA labels
-      - Color contrast
-      - Focus management
-    estimationPercent: 10
-    tags: ["accessibility", "a11y", "quality"]
-    activity: "Testing"
-
-  - id: "component-tests"
-    title: "Component Testing"
-    description: |
-      Write comprehensive tests:
-      - Jest unit tests
-      - React Testing Library
-      - Test user interactions
-      - Snapshot tests
-    estimationPercent: 15
-    tags: ["testing", "quality"]
-    activity: "Testing"
-    dependsOn:
-      - "component-logic"
-
-# Estimation configuration
-estimation:
-  strategy: "percentage"
-  source: "Microsoft.VSTS.Scheduling.StoryPoints"
-  rounding: "nearest"
-  minimumTaskPoints: 0.5
-
-# Validation
-validation:
-  totalEstimationMustBe: 100
-  minTasks: 4
-
-# Metadata
-metadata:
-  category: "Frontend Development"
-  difficulty: "intermediate"
-  recommendedFor:
-    - "React components"
-    - "UI features"
-    - "User interfaces"
-  estimationGuidelines: |
-    Best for stories sized 3-8 points.
-    Complex UIs with animations may need additional tasks.
-  examples:
-    - "User profile page"
-    - "Data table component"
-    - "Form wizard"

package/examples/fullstack.yaml

@@ -1,167 +0,0 @@
-version: "1.0"
-name: "Fullstack Feature"
-description: "Complete fullstack feature with frontend and backend tasks"
-author: "Atomize"
-tags: ["fullstack", "frontend", "backend"]
-
-filter:
-  workItemTypes:
-    - "User Story"
-  states:
-    - "New"
-    - "Active"
-  tags:
-    include:
-      - "fullstack"
-  excludeIfHasTasks: true
-
-tasks:
-  # Design Phase
-  - id: "design-overview"
-    title: "Technical Design"
-    description: |
-      Create comprehensive technical design:
-      - Architecture diagram
-      - API contract definition
-      - Data models
-      - UI/UX flow
-    estimationPercent: 10
-    tags: ["design", "planning"]
-    activity: "Design"
-
-  # Backend Tasks
-  - id: "backend-api"
-    title: " Backend API Implementation"
-    description: |
-      Implement backend API:
-      - API endpoints
-      - Business logic
-      - Validation
-      - Error handling
-    estimationPercent: 20
-    tags: ["backend", "api"]
-    activity: "Development"
-    dependsOn: ["design-overview"]
-
-  - id: "database"
-    title: "Database Implementation"
-    description: |
-      Database changes:
-      - Schema migrations
-      - Models
-      - Queries
-      - Indexes
-    estimationPercent: 15
-    tags: ["database", "backend"]
-    activity: "Development"
-    condition:
-      field: tags
-      operator: contains
-      value: database
-
-  - id: "backend-tests"
-    title: "Backend Tests"
-    description: |
-      Backend test coverage:
-      - Unit tests (80%+)
-      - Integration tests
-      - API endpoint tests
-    estimationPercent: 10
-    tags: ["testing", "backend"]
-    activity: "Testing"
-    dependsOn: ["backend-api"]
-
-  # Frontend Tasks
-  - id: "frontend-components"
-    title: "Frontend Components"
-    description: |
-      Build React components:
-      - Component structure
-      - Props interfaces
-      - State management
-      - Event handlers
-    estimationPercent: 20
-    tags: ["frontend", "react"]
-    activity: "Development"
-    dependsOn: ["design-overview"]
-
-  - id: "frontend-styling"
-    title: "Styling & Responsive Design"
-    description: |
-      Apply styles:
-      - CSS/Tailwind
-      - Mobile responsive
-      - Theme integration
-    estimationPercent: 10
-    tags: ["frontend", "styling"]
-    activity: "Development"
-
-  - id: "frontend-tests"
-    title: "Frontend Tests"
-    description: |
-      Frontend test coverage:
-      - Component tests
-      - User interaction tests
-      - Snapshot tests
-    estimationPercent: 8
-    tags: ["testing", "frontend"]
-    activity: "Testing"
-    dependsOn: ["frontend-components"]
-
-  # Integration
-  - id: "integration"
-    title: "Frontend-Backend Integration"
-    description: |
-      Connect frontend to backend:
-      - API integration
-      - Error handling
-      - Loading states
-      - Data flow testing
-    estimationPercent: 12
-    tags: ["integration"]
-    activity: "Development"
-    dependsOn: ["backend-api", "frontend-components"]
-
-  # Documentation & Review
-  - id: "documentation"
-    title: "Documentation"
-    description: |
-      Complete documentation:
-      - API documentation
-      - Component documentation
-      - README updates
-      - Deployment guide
-    estimationPercent: 5
-    tags: ["documentation"]
-    activity: "Documentation"
-
-# Estimation configuration
-estimation:
-  strategy: "percentage"
-  source: "Microsoft.VSTS.Scheduling.StoryPoints"
-  rounding: "nearest"
-  minimumTaskPoints: 0.5
-
-# Validation
-validation:
-  totalEstimationRange:
-    min: 95
-    max: 105
-  minTasks: 5
-
-# Metadata
-metadata:
-  category: "Fullstack Development"
-  difficulty: "advanced"
-  recommendedFor:
-    - "Full features with UI and API"
-    - "Complete user flows"
-    - "End-to-end features"
-  estimationGuidelines: |
-    Best for stories sized 5-13 points.
-    This template covers both frontend and backend.
-    Adjust tasks based on complexity.
-  examples:
-    - "User registration flow"
-    - "Dashboard with data visualization"
-    - "Search and filter feature"