tapps-agents 3.5.39__py3-none-any.whl → 3.5.40__py3-none-any.whl

tapps_agents/agents/orchestrator/SKILL.md

@@ -1,238 +0,0 @@
-# Orchestrator Agent - Skill Definition
-
-> NOTE: Cursor uses the canonical Skills in `.claude/skills/`.  
-> This file is framework documentation; prefer `.claude/skills/orchestrator/SKILL.md` for Cursor.
-
-## Purpose
-
-The Orchestrator Agent coordinates YAML-defined workflows and makes gate decisions. It is responsible for:
-
-- Loading and executing workflows from YAML definitions
-- Making gate decisions based on scoring and conditions
-- Routing to appropriate workflows (Greenfield/Brownfield)
-- Tracking workflow state and progress
-- Coordinating agent execution within workflows
-
-## Permissions
-
-- **Read**: ✅
-- **Write**: ❌
-- **Edit**: ❌
-- **Grep**: ✅
-- **Glob**: ✅
-- **Bash**: ❌
-
-**Type**: Read-only agent (coordination only, no code modification)
-
-## Commands
-
-### `*workflow-list`
-
-List all available workflows in the `workflows/` directory.
-
-**Example:**
-```bash
-tapps-agents orchestrator *workflow-list
-```
-
-**Returns:**
-```json
-{
-  "workflows": [
-    {
-      "id": "example-feature-development",
-      "name": "Example Feature Development Workflow",
-      "description": "Standard workflow for new feature implementation",
-      "version": "1.0.0",
-      "type": "greenfield",
-      "file": "workflows/example-feature-development.yaml"
-    }
-  ]
-}
-```
-
-### `*workflow-start {workflow_id}`
-
-Start a workflow by ID.
-
-**Example:**
-```bash
-tapps-agents orchestrator *workflow-start example-feature-development
-```
-
-**Returns:**
-```json
-{
-  "success": true,
-  "workflow_id": "example-feature-development",
-  "workflow_name": "Example Feature Development Workflow",
-  "status": "running",
-  "current_step": "requirements",
-  "message": "Workflow 'Example Feature Development Workflow' started"
-}
-```
-
-### `*workflow-status`
-
-Get the current workflow execution status.
-
-**Example:**
-```bash
-tapps-agents orchestrator *workflow-status
-```
-
-**Returns:**
-```json
-{
-  "workflow_id": "example-feature-development",
-  "status": "running",
-  "current_step": "planning",
-  "current_step_details": {
-    "id": "planning",
-    "agent": "planner",
-    "action": "create_stories"
-  },
-  "completed_steps": ["requirements"],
-  "skipped_steps": [],
-  "artifacts_count": 1,
-  "can_proceed": true
-}
-```
-
-### `*workflow-next`
-
-Get information about the next step in the workflow.
-
-**Example:**
-```bash
-tapps-agents orchestrator *workflow-next
-```
-
-**Returns:**
-```json
-{
-  "next_step": {
-    "id": "design",
-    "agent": "architect",
-    "action": "design_system",
-    "context_tier": 2,
-    "requires": ["requirements.md", "stories/"],
-    "creates": ["architecture.md"]
-  }
-}
-```
-
-### `*workflow-skip {step_id}`
-
-Skip an optional step in the workflow.
-
-**Example:**
-```bash
-tapps-agents orchestrator *workflow-skip review
-```
-
-**Returns:**
-```json
-{
-  "success": true,
-  "message": "Step 'review' skipped",
-  "current_step": "testing"
-}
-```
-
-### `*workflow-resume`
-
-Resume an interrupted workflow (loads state from persistence).
-
-**Example:**
-```bash
-tapps-agents orchestrator *workflow-resume
-```
-
-### `*gate {condition}`
-
-Make a gate decision based on condition and scoring data.
-
-**Example:**
-```bash
-tapps-agents orchestrator *gate --condition "scoring.passed == true" --scoring-data '{"passed": true, "overall_score": 85}'
-```
-
-**Returns:**
-```json
-{
-  "passed": true,
-  "condition": "scoring.passed == true",
-  "scoring": {
-    "passed": true,
-    "overall_score": 85
-  },
-  "message": "Gate passed"
-}
-```
-
-### `*help`
-
-Show help for orchestrator commands.
-
-## Workflow Integration
-
-The Orchestrator Agent integrates with the Workflow Engine to:
-
-1. **Load Workflows**: Parse YAML workflow definitions
-2. **Execute Steps**: Coordinate agent execution for each step
-3. **Track Artifacts**: Monitor artifact creation and dependencies
-4. **Make Gates**: Evaluate conditions and scoring to determine workflow progression
-5. **Handle Branching**: Route to different steps based on gate decisions
-
-## Gate Decision Logic
-
-The orchestrator evaluates gate conditions using:
-
-- **Scoring Data**: Results from reviewer agent (overall_score, passed, etc.)
-- **Conditions**: String expressions like "scoring.passed == true" or "overall_score >= 70"
-- **Thresholds**: Minimum scores for passing gates
-
-**Gate Outcomes:**
-- **Pass**: Workflow proceeds to `on_pass` step
-- **Fail**: Workflow loops back to `on_fail` step (typically for retry)
-
-## Context Tier Usage
-
-The orchestrator uses **Tier 1** context (minimal) since it only coordinates workflows and doesn't analyze code.
-
-## Integration with Other Agents
-
-The orchestrator coordinates:
-
-- **Planner**: Creates stories and plans
-- **Architect**: Designs system architecture
-- **Implementer**: Generates code
-- **Reviewer**: Reviews code and provides scoring
-- **Tester**: Generates and runs tests
-- **Debugger**: Analyzes errors
-- **Documenter**: Generates documentation
-
-## Example Workflow Execution
-
-```yaml
-# workflows/example-feature-development.yaml
-workflow:
-  id: example-feature-development
-  steps:
-    - id: review
-      agent: reviewer
-      action: review_code
-      gate:
-        condition: "scoring.passed == true"
-        on_pass: testing
-        on_fail: implementation
-```
-
-**Execution Flow:**
-1. Orchestrator starts workflow
-2. Reviewer agent reviews code
-3. Orchestrator evaluates gate: `scoring.passed == true`
-4. If passed → proceed to testing
-5. If failed → loop back to implementation
-

tapps_agents/agents/planner/story_template.md

@@ -1,37 +0,0 @@
-# User Story Template
-
-```yaml
-story_id: <auto-generated>
-title: <short descriptive title>
-description: <detailed description>
-epic: <epic or feature area>
-domain: <business domain>
-priority: <high|medium|low>
-complexity: <1-5 estimate>
-status: <draft|ready|in-progress|done>
-created_at: <timestamp>
-created_by: planner
-```
-
-## Acceptance Criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2
-- [ ] Criterion 3
-
-## Tasks
-
-1. Task 1
-2. Task 2
-3. Task 3
-
-## Technical Notes
-
-(Technical considerations, dependencies, etc.)
-
-## Dependencies
-
-- Related stories: []
-- Blocks: []
-- Blocked by: []
-

tapps_agents/agents/reviewer/templates/quality-dashboard.html.j2

@@ -1,150 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="UTF-8">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>Quality Analysis Dashboard</title>
-  <style>
-    body {
-      font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;
-      max-width: 1200px;
-      margin: 0 auto;
-      padding: 20px;
-      background-color: #f5f5f5;
-    }
-    .header {
-      background: white;
-      padding: 20px;
-      border-radius: 8px;
-      margin-bottom: 20px;
-      box-shadow: 0 2px 4px rgba(0,0,0,0.1);
-    }
-    .status {
-      display: inline-block;
-      padding: 8px 16px;
-      border-radius: 4px;
-      color: white;
-      font-weight: bold;
-      background-color: {{ status_color }};
-      margin: 10px 0;
-    }
-    .metrics {
-      display: grid;
-      grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
-      gap: 20px;
-      margin-bottom: 20px;
-    }
-    .metric-card {
-      background: white;
-      padding: 20px;
-      border-radius: 8px;
-      box-shadow: 0 2px 4px rgba(0,0,0,0.1);
-    }
-    .metric-label {
-      font-size: 14px;
-      color: #666;
-      margin-bottom: 8px;
-    }
-    .metric-value {
-      font-size: 32px;
-      font-weight: bold;
-      color: #333;
-    }
-    table {
-      width: 100%;
-      border-collapse: collapse;
-      background: white;
-      border-radius: 8px;
-      overflow: hidden;
-      box-shadow: 0 2px 4px rgba(0,0,0,0.1);
-    }
-    th, td {
-      padding: 12px;
-      text-align: left;
-      border-bottom: 1px solid #ddd;
-    }
-    th {
-      background-color: #f8f9fa;
-      font-weight: 600;
-    }
-    .footer {
-      text-align: center;
-      color: #666;
-      margin-top: 40px;
-      font-size: 12px;
-    }
-  </style>
-</head>
-<body>
-  <div class="header">
-    <h1>Quality Analysis Dashboard</h1>
-    <p><strong>Generated:</strong> {{ generated_at }}</p>
-    <p><strong>Project:</strong> {{ project_name }}</p>
-    <p><strong>Version:</strong> {{ version }}</p>
-    <div class="status">{{ status_text }}</div>
-    <p><strong>Overall Score:</strong> {{ overall_score }}/100 (Threshold: {{ overall_threshold }})</p>
-  </div>
-
-  <div class="metrics">
-    <div class="metric-card">
-      <div class="metric-label">Complexity</div>
-      <div class="metric-value">{{ complexity_score }}</div>
-    </div>
-    <div class="metric-card">
-      <div class="metric-label">Security</div>
-      <div class="metric-value">{{ security_score }}</div>
-    </div>
-    <div class="metric-card">
-      <div class="metric-label">Maintainability</div>
-      <div class="metric-value">{{ maintainability_score }}</div>
-    </div>
-    <div class="metric-card">
-      <div class="metric-label">Test Coverage</div>
-      <div class="metric-value">{{ test_coverage_score }}</div>
-    </div>
-    <div class="metric-card">
-      <div class="metric-label">Performance</div>
-      <div class="metric-value">{{ performance_score }}</div>
-    </div>
-    <div class="metric-card">
-      <div class="metric-label">Linting</div>
-      <div class="metric-value">{{ linting_score }}</div>
-    </div>
-    <div class="metric-card">
-      <div class="metric-label">Type Checking</div>
-      <div class="metric-value">{{ type_checking_score }}</div>
-    </div>
-  </div>
-
-  {% if files %}
-  <h2>File-Level Analysis</h2>
-  <table>
-    <thead>
-      <tr>
-        <th>File</th>
-        <th>Overall Score</th>
-        <th>Complexity</th>
-        <th>Security</th>
-        <th>Maintainability</th>
-      </tr>
-    </thead>
-    <tbody>
-      {% for f in files %}
-      <tr>
-        <td>{{ f.file }}</td>
-        <td>{{ f.overall_score }}</td>
-        <td>{{ f.complexity_score }}</td>
-        <td>{{ f.security_score }}</td>
-        <td>{{ f.maintainability_score }}</td>
-      </tr>
-      {% endfor %}
-    </tbody>
-  </table>
-  {% endif %}
-
-  <div class="footer">
-    Generated by TappsCodingAgents Quality Analysis System
-  </div>
-</body>
-</html>
-

tapps_agents/agents/tester/SKILL.md

@@ -1,71 +0,0 @@
----
-name: tester
-description: Generate and run tests for code. Use when creating unit tests, integration tests, or running test suites.
-allowed-tools: Read, Write, Edit, Grep, Glob, Bash
-model_profile: tester_profile
----
-
-# Tester Agent
-
-## Identity
-
-You are a senior QA engineer focused on creating comprehensive, maintainable tests that ensure code quality and reliability.
-
-## Instructions
-
-1. Analyze code structure to identify test cases
-2. Generate unit tests for all public functions and methods
-3. Generate integration tests for module interactions
-4. Follow project test patterns and conventions
-5. Include edge cases and error handling
-6. Mock external dependencies appropriately
-7. Run tests and report coverage
-
-## Capabilities
-
-- **Test Generation**: Create unit and integration tests from code analysis
-- **Test Execution**: Run pytest test suites
-- **Coverage Reporting**: Track and report test coverage
-- **Code Analysis**: Analyze code structure to identify test targets
-
-## Commands
-
-- `*test <file>` - Generate and run tests for a file
-- `*generate-tests <file>` - Generate tests without running
-- `*run-tests [path]` - Run existing tests
-
-## Examples
-
-```bash
-# Generate and run tests
-*test calculator.py
-
-# Generate integration tests
-*test api.py --integration
-
-# Generate tests only (don't run)
-*generate-tests utils.py
-
-# Run all tests
-*run-tests
-
-# Run specific test file
-*run-tests tests/test_calculator.py
-```
-
-## Test Quality Standards
-
-- **Coverage**: Target 80%+ coverage
-- **Naming**: Descriptive test names (test_function_name_scenario)
-- **Structure**: Arrange-Act-Assert pattern
-- **Isolation**: Tests should be independent
-- **Mocking**: Mock external dependencies
-- **Documentation**: Include docstrings for complex tests
-
-## Test Framework
-
-Default: pytest
-- Use pytest fixtures for setup/teardown
-- Use pytest.mark for test categorization
-- Use pytest.parametrize for parameterized tests
-