doit-toolkit-cli 0.1.10__py3-none-any.whl

doit_cli/templates/hooks/post-merge.sh

@@ -0,0 +1,75 @@
+#!/usr/bin/env bash
+# Post-merge hook installed by doit
+# This hook auto-completes fixit workflows when fix branches are merged
+
+# Exit on error
+set -e
+
+# Check if doit is available
+if ! command -v doit &> /dev/null; then
+    exit 0
+fi
+
+# Get the name of the branch that was merged
+# SQUASH_MSG contains the branch name for squash merges
+# Otherwise we need to check reflog
+
+# Check if we have a squash commit message file
+if [ -f ".git/SQUASH_MSG" ]; then
+    # Try to extract branch name from squash message
+    MERGED_BRANCH=$(head -1 .git/SQUASH_MSG | grep -oE "fix/[0-9]+-[a-z0-9-]+" || true)
+fi
+
+# Fallback: check git reflog for recent merge
+if [ -z "$MERGED_BRANCH" ]; then
+    # Get the most recent merge line from reflog
+    REFLOG_MERGE=$(git reflog --grep-reflog="merge" -1 2>/dev/null || true)
+    if [ -n "$REFLOG_MERGE" ]; then
+        MERGED_BRANCH=$(echo "$REFLOG_MERGE" | grep -oE "fix/[0-9]+-[a-z0-9-]+" || true)
+    fi
+fi
+
+# Fallback: Check ORIG_HEAD which points to the tip before the merge
+if [ -z "$MERGED_BRANCH" ]; then
+    # Get the branch that was merged using the second parent of HEAD
+    PARENT2=$(git rev-parse HEAD^2 2>/dev/null || true)
+    if [ -n "$PARENT2" ]; then
+        # Find branch containing this commit
+        MERGED_BRANCH=$(git branch -a --contains "$PARENT2" 2>/dev/null | grep -oE "fix/[0-9]+-[a-z0-9-]+" | head -1 || true)
+    fi
+fi
+
+# If we found a fix branch, complete the workflow
+if [ -n "$MERGED_BRANCH" ]; then
+    # Extract issue ID from branch name (fix/{issue_id}-{slug})
+    ISSUE_ID=$(echo "$MERGED_BRANCH" | grep -oE "fix/([0-9]+)" | sed 's/fix\///')
+
+    if [ -n "$ISSUE_ID" ]; then
+        echo "🔧 Detected merge of fix branch: $MERGED_BRANCH"
+        echo "📋 Auto-completing workflow for issue #$ISSUE_ID..."
+
+        # Call doit to complete the workflow
+        # This will close the GitHub issue and mark the workflow as completed
+        python -c "
+from doit_cli.services.fixit_service import FixitService
+from doit_cli.services.github_service import GitHubService
+from doit_cli.services.state_manager import StateManager
+
+try:
+    service = FixitService()
+    workflow = service.get_workflow($ISSUE_ID)
+    if workflow:
+        success = service.complete_workflow($ISSUE_ID, close_issue=True)
+        if success:
+            print('✅ Workflow completed and issue #$ISSUE_ID closed!')
+        else:
+            print('⚠️  Could not complete workflow (may already be completed)')
+    else:
+        print('ℹ️  No active workflow found for issue #$ISSUE_ID')
+except Exception as e:
+    print(f'⚠️  Could not auto-complete workflow: {e}')
+" 2>/dev/null || echo "⚠️  Fixit workflow completion skipped (doit-cli not in environment)"
+    fi
+fi
+
+exit 0

doit_cli/templates/hooks/pre-commit.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+# Pre-commit hook installed by doit
+# This hook validates workflow compliance before allowing commits
+
+# Exit on error
+set -e
+
+# Check if doit is available
+if ! command -v doit &> /dev/null; then
+    echo "Warning: doit command not found in PATH"
+    echo "Skipping pre-commit validation"
+    exit 0
+fi
+
+# Run pre-commit validation
+# Note: The doit validate command only needs the hook type, not shell arguments.
+exec doit hooks validate pre-commit

doit_cli/templates/hooks/pre-push.sh

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+# Pre-push hook installed by doit
+# This hook validates workflow artifacts before allowing pushes
+
+# Exit on error
+set -e
+
+# Check if doit is available
+if ! command -v doit &> /dev/null; then
+    echo "Warning: doit command not found in PATH"
+    echo "Skipping pre-push validation"
+    exit 0
+fi
+
+# Run pre-push validation
+# Note: Git passes remote name and URL as arguments, and ref info via stdin.
+# The doit validate command only needs the hook type, not git's arguments.
+exec doit hooks validate pre-push

doit_cli/templates/memory/completed_roadmap.md

@@ -0,0 +1,50 @@
+# Completed Roadmap Items
+
+**Project**: [PROJECT_NAME]
+**Created**: [DATE]
+**Purpose**: Historical record of completed roadmap items for AI context and project history
+
+---
+
+## Recently Completed
+
+<!-- Last 20 completed items - older items are archived below -->
+
+| Item | Original Priority | Completed Date | Feature Branch | Notes |
+|------|-------------------|----------------|----------------|-------|
+| [COMPLETED_ITEM] | [P1-P4] | [DATE] | `[###-feature-name]` | [NOTES] |
+
+---
+
+## Archive
+
+<!-- Older completed items (beyond 20 most recent) -->
+
+<details>
+<summary>Archived Items (click to expand)</summary>
+
+| Item | Original Priority | Completed Date | Feature Branch |
+|------|-------------------|----------------|----------------|
+<!-- Older items will be moved here automatically -->
+
+</details>
+
+---
+
+## Statistics
+
+- **Total Items Completed**: [COUNT]
+- **P1 Items Completed**: [P1_COUNT]
+- **P2 Items Completed**: [P2_COUNT]
+- **P3 Items Completed**: [P3_COUNT]
+- **P4 Items Completed**: [P4_COUNT]
+
+---
+
+## Notes
+
+- This file is maintained automatically by `/doit.checkin` when features complete
+- Items are matched by feature branch reference `[###-feature-name]`
+- Only the 20 most recent items are kept in "Recently Completed"
+- Older items are moved to the Archive section
+- Use this history to understand project evolution and past decisions

doit_cli/templates/memory/constitution.md

@@ -0,0 +1,125 @@
+# [PROJECT_NAME] Constitution
+
+<!-- Example: Spec Constitution, TaskFlow Constitution, etc. -->
+
+## Purpose & Goals
+
+### Project Purpose
+
+[PROJECT_PURPOSE]
+<!-- Example: A CLI tool for managing feature specifications and task tracking -->
+
+### Success Criteria
+
+[SUCCESS_CRITERIA]
+<!-- Example:
+- Reduce feature specification time by 50%
+- Enable consistent task breakdown across teams
+- Support multiple AI assistants for development -->
+
+## Tech Stack
+
+### Languages
+
+[PRIMARY_LANGUAGE]
+<!-- Example: Python 3.11+ (primary), TypeScript (frontend) -->
+
+### Frameworks
+
+[FRAMEWORKS]
+<!-- Example: FastAPI (API), React (frontend), pytest (testing) -->
+
+### Libraries
+
+[KEY_LIBRARIES]
+<!-- Example: Pydantic (validation), SQLAlchemy (ORM), Rich (CLI) -->
+
+## Infrastructure
+
+### Hosting
+
+[HOSTING_PLATFORM]
+<!-- Example: AWS ECS, Google Cloud Run, Azure Container Apps, Self-hosted -->
+
+### Cloud Provider
+
+[CLOUD_PROVIDER]
+<!-- Example: AWS, GCP, Azure, Multi-cloud, On-premises -->
+
+### Database
+
+[DATABASE]
+<!-- Example: PostgreSQL (primary), Redis (cache), none -->
+
+## Deployment
+
+### CI/CD Pipeline
+
+[CICD_PIPELINE]
+<!-- Example: GitHub Actions, GitLab CI, Jenkins, CircleCI -->
+
+### Deployment Strategy
+
+[DEPLOYMENT_STRATEGY]
+<!-- Example: Blue-green, Rolling, Canary, Manual -->
+
+### Environments
+
+[ENVIRONMENTS]
+<!-- Example: dev, staging, production -->
+
+## Core Principles
+
+### [PRINCIPLE_1_NAME]
+
+<!-- Example: I. Library-First -->
+[PRINCIPLE_1_DESCRIPTION]
+<!-- Example: Every feature starts as a standalone library; Libraries must be self-contained, independently testable, documented; Clear purpose required - no organizational-only libraries -->
+
+### [PRINCIPLE_2_NAME]
+
+<!-- Example: II. CLI Interface -->
+[PRINCIPLE_2_DESCRIPTION]
+<!-- Example: Every library exposes functionality via CLI; Text in/out protocol: stdin/args → stdout, errors → stderr; Support JSON + human-readable formats -->
+
+### [PRINCIPLE_3_NAME]
+
+<!-- Example: III. Test-First (NON-NEGOTIABLE) -->
+[PRINCIPLE_3_DESCRIPTION]
+<!-- Example: TDD mandatory: Tests written → User approved → Tests fail → Then implement; Red-Green-Refactor cycle strictly enforced -->
+
+### [PRINCIPLE_4_NAME]
+
+<!-- Example: IV. Integration Testing -->
+[PRINCIPLE_4_DESCRIPTION]
+<!-- Example: Focus areas requiring integration tests: New library contract tests, Contract changes, Inter-service communication, Shared schemas -->
+
+### [PRINCIPLE_5_NAME]
+
+<!-- Example: V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity -->
+[PRINCIPLE_5_DESCRIPTION]
+<!-- Example: Text I/O ensures debuggability; Structured logging required; Or: MAJOR.MINOR.BUILD format; Or: Start simple, YAGNI principles -->
+
+## [SECTION_2_NAME]
+
+<!-- Example: Additional Constraints, Security Requirements, Performance Standards, etc. -->
+
+[SECTION_2_CONTENT]
+<!-- Example: Technology stack requirements, compliance standards, deployment policies, etc. -->
+
+## [SECTION_3_NAME]
+
+<!-- Example: Development Workflow, Review Process, Quality Gates, etc. -->
+
+[SECTION_3_CONTENT]
+<!-- Example: Code review requirements, testing gates, deployment approval process, etc. -->
+
+## Governance
+
+<!-- Example: Constitution supersedes all other practices; Amendments require documentation, approval, migration plan -->
+
+[GOVERNANCE_RULES]
+<!-- Example: All PRs/reviews must verify compliance; Complexity must be justified; Use [GUIDANCE_FILE] for runtime development guidance -->
+
+**Version**: [CONSTITUTION_VERSION] | **Ratified**: [RATIFICATION_DATE] | **Last Amended**: [LAST_AMENDED_DATE]
+<!-- Example: Version: 2.1.1 | Ratified: 2025-06-13 | Last Amended: 2025-07-16 -->

doit_cli/templates/memory/roadmap.md

@@ -0,0 +1,61 @@
+# Project Roadmap
+
+**Project**: [PROJECT_NAME]
+**Last Updated**: [DATE]
+**Managed by**: `/doit.roadmapit`
+
+## Vision
+
+[PROJECT_VISION]
+
+---
+
+## Active Requirements
+
+### P1 - Critical (Must Have for MVP)
+
+<!-- Items that are essential for minimum viable product or blocking other work -->
+
+- [ ] [P1_ITEM_1] `[feature-branch-reference]`
+  - **Rationale**: [Why this is critical]
+
+### P2 - High Priority (Significant Business Value)
+
+<!-- Items with high business value, scheduled for near-term delivery -->
+
+- [ ] [P2_ITEM_1] `[feature-branch-reference]`
+  - **Rationale**: [Why this is high priority]
+
+### P3 - Medium Priority (Valuable)
+
+<!-- Items that add value but can wait for later iterations -->
+
+- [ ] [P3_ITEM_1] `[feature-branch-reference]`
+  - **Rationale**: [Why this is medium priority]
+
+### P4 - Low Priority (Nice to Have)
+
+<!-- Items in the backlog, considered for future development -->
+
+- [ ] [P4_ITEM_1] `[feature-branch-reference]`
+  - **Rationale**: [Why this is low priority]
+
+---
+
+## Deferred Items
+
+<!-- Items that were considered but intentionally deferred with reason -->
+
+| Item | Original Priority | Deferred Date | Reason |
+|------|-------------------|---------------|--------|
+| [DEFERRED_ITEM] | [P1-P4] | [DATE] | [REASON] |
+
+---
+
+## Notes
+
+- Items marked with `[###-feature-name]` reference link to feature branches for tracking
+- When a feature completes via `/doit.checkin`, matching items are moved to `completed_roadmap.md`
+- Use `/doit.roadmapit add [item]` to add new items
+- Use `/doit.roadmapit defer [item]` to move items to deferred section
+- Use `/doit.roadmapit reprioritize` to change item priorities

doit_cli/templates/plan-template.md

@@ -0,0 +1,146 @@
+# Implementation Plan: [FEATURE]
+
+**Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
+**Input**: Feature specification from `/specs/[###-feature-name]/spec.md`
+
+**Note**: This template is filled in by the `/doit.planit` command. See `.claude/commands/doit.planit.md` for the execution workflow.
+
+## Summary
+
+[Extract from feature spec: primary requirement + technical approach from research]
+
+## Technical Context
+
+<!--
+  ACTION REQUIRED: Replace the content in this section with the technical details
+  for the project. The structure here is presented in advisory capacity to guide
+  the iteration process.
+-->
+
+**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]
+**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]
+**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]
+**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]
+**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
+**Project Type**: [single/web/mobile - determines source structure]
+**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]
+**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]
+**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]
+
+## Architecture Overview
+
+<!--
+  AUTO-GENERATED: This section is populated by /doit.planit based on Technical Context above.
+  Shows the high-level system architecture with component layers.
+  Regenerate by running /doit.planit again.
+-->
+
+<!-- BEGIN:AUTO-GENERATED section="architecture" -->
+```mermaid
+flowchart TD
+    subgraph "Presentation"
+        UI[UI Layer]
+    end
+    subgraph "Application"
+        API[API Layer]
+        SVC[Service Layer]
+    end
+    subgraph "Data"
+        DB[(Database)]
+    end
+    UI --> API --> SVC --> DB
+```
+<!-- END:AUTO-GENERATED -->
+
+## Component Dependencies *(include if multiple services/components)*
+
+<!--
+  AUTO-GENERATED: This section is populated by /doit.planit when multiple services are defined.
+  Shows dependencies between services and components.
+  If only one service, this section should be omitted.
+-->
+
+<!-- BEGIN:AUTO-GENERATED section="component-dependencies" -->
+```mermaid
+flowchart TD
+    AUTH[Auth Service] --> USER[User Service]
+    CORE[Core Service] --> USER
+    CORE --> DATA[Data Service]
+```
+<!-- END:AUTO-GENERATED -->
+
+## Constitution Check
+
+*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
+
+[Gates determined based on constitution file]
+
+## Project Structure
+
+### Documentation (this feature)
+
+```text
+specs/[###-feature]/
+├── plan.md              # This file (/doit.planit command output)
+├── research.md          # Phase 0 output (/doit.planit command)
+├── data-model.md        # Phase 1 output (/doit.planit command)
+├── quickstart.md        # Phase 1 output (/doit.planit command)
+├── contracts/           # Phase 1 output (/doit.planit command)
+└── tasks.md             # Phase 2 output (/doit.taskit command - NOT created by /doit.planit)
+```
+
+### Source Code (repository root)
+<!--
+  ACTION REQUIRED: Replace the placeholder tree below with the concrete layout
+  for this feature. Delete unused options and expand the chosen structure with
+  real paths (e.g., apps/admin, packages/something). The delivered plan must
+  not include Option labels.
+-->
+
+```text
+# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
+src/
+├── models/
+├── services/
+├── cli/
+└── lib/
+
+tests/
+├── contract/
+├── integration/
+└── unit/
+
+# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
+backend/
+├── src/
+│   ├── models/
+│   ├── services/
+│   └── api/
+└── tests/
+
+frontend/
+├── src/
+│   ├── components/
+│   ├── pages/
+│   └── services/
+└── tests/
+
+# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
+api/
+└── [same as backend above]
+
+ios/ or android/
+└── [platform-specific structure: feature modules, UI flows, platform tests]
+```
+
+**Structure Decision**: [Document the selected structure and reference the real
+directories captured above]
+
+## Complexity Tracking
+
+> **Fill ONLY if Constitution Check has violations that must be justified**
+
+| Violation | Why Needed | Simpler Alternative Rejected Because |
+|-----------|------------|-------------------------------------|
+| [e.g., 4th project] | [current need] | [why 3 projects insufficient] |
+| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient] |

doit_cli/templates/scripts/bash/check-prerequisites.sh

@@ -0,0 +1,166 @@
+#!/usr/bin/env bash
+
+# Consolidated prerequisite checking script
+#
+# This script provides unified prerequisite checking for Spec-Driven Development workflow.
+# It replaces the functionality previously spread across multiple scripts.
+#
+# Usage: ./check-prerequisites.sh [OPTIONS]
+#
+# OPTIONS:
+#   --json              Output in JSON format
+#   --require-tasks     Require tasks.md to exist (for implementation phase)
+#   --include-tasks     Include tasks.md in AVAILABLE_DOCS list
+#   --paths-only        Only output path variables (no validation)
+#   --help, -h          Show help message
+#
+# OUTPUTS:
+#   JSON mode: {"FEATURE_DIR":"...", "AVAILABLE_DOCS":["..."]}
+#   Text mode: FEATURE_DIR:... \n AVAILABLE_DOCS: \n ✓/✗ file.md
+#   Paths only: REPO_ROOT: ... \n BRANCH: ... \n FEATURE_DIR: ... etc.
+
+set -e
+
+# Parse command line arguments
+JSON_MODE=false
+REQUIRE_TASKS=false
+INCLUDE_TASKS=false
+PATHS_ONLY=false
+
+for arg in "$@"; do
+    case "$arg" in
+        --json)
+            JSON_MODE=true
+            ;;
+        --require-tasks)
+            REQUIRE_TASKS=true
+            ;;
+        --include-tasks)
+            INCLUDE_TASKS=true
+            ;;
+        --paths-only)
+            PATHS_ONLY=true
+            ;;
+        --help|-h)
+            cat << 'EOF'
+Usage: check-prerequisites.sh [OPTIONS]
+
+Consolidated prerequisite checking for Spec-Driven Development workflow.
+
+OPTIONS:
+  --json              Output in JSON format
+  --require-tasks     Require tasks.md to exist (for implementation phase)
+  --include-tasks     Include tasks.md in AVAILABLE_DOCS list
+  --paths-only        Only output path variables (no prerequisite validation)
+  --help, -h          Show this help message
+
+EXAMPLES:
+  # Check task prerequisites (plan.md required)
+  ./check-prerequisites.sh --json
+  
+  # Check implementation prerequisites (plan.md + tasks.md required)
+  ./check-prerequisites.sh --json --require-tasks --include-tasks
+  
+  # Get feature paths only (no validation)
+  ./check-prerequisites.sh --paths-only
+  
+EOF
+            exit 0
+            ;;
+        *)
+            echo "ERROR: Unknown option '$arg'. Use --help for usage information." >&2
+            exit 1
+            ;;
+    esac
+done
+
+# Source common functions
+SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "$SCRIPT_DIR/common.sh"
+
+# Get feature paths and validate branch
+eval $(get_feature_paths)
+check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
+
+# If paths-only mode, output paths and exit (support JSON + paths-only combined)
+if $PATHS_ONLY; then
+    if $JSON_MODE; then
+        # Minimal JSON paths payload (no validation performed)
+        printf '{"REPO_ROOT":"%s","BRANCH":"%s","FEATURE_DIR":"%s","FEATURE_SPEC":"%s","IMPL_PLAN":"%s","TASKS":"%s"}\n' \
+            "$REPO_ROOT" "$CURRENT_BRANCH" "$FEATURE_DIR" "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS"
+    else
+        echo "REPO_ROOT: $REPO_ROOT"
+        echo "BRANCH: $CURRENT_BRANCH"
+        echo "FEATURE_DIR: $FEATURE_DIR"
+        echo "FEATURE_SPEC: $FEATURE_SPEC"
+        echo "IMPL_PLAN: $IMPL_PLAN"
+        echo "TASKS: $TASKS"
+    fi
+    exit 0
+fi
+
+# Validate required directories and files
+if [[ ! -d "$FEATURE_DIR" ]]; then
+    echo "ERROR: Feature directory not found: $FEATURE_DIR" >&2
+    echo "Run /doit.doit first to create the feature structure." >&2
+    exit 1
+fi
+
+if [[ ! -f "$IMPL_PLAN" ]]; then
+    echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
+    echo "Run /doit.plan first to create the implementation plan." >&2
+    exit 1
+fi
+
+# Check for tasks.md if required
+if $REQUIRE_TASKS && [[ ! -f "$TASKS" ]]; then
+    echo "ERROR: tasks.md not found in $FEATURE_DIR" >&2
+    echo "Run /doit.tasks first to create the task list." >&2
+    exit 1
+fi
+
+# Build list of available documents
+docs=()
+
+# Always check these optional docs
+[[ -f "$RESEARCH" ]] && docs+=("research.md")
+[[ -f "$DATA_MODEL" ]] && docs+=("data-model.md")
+
+# Check contracts directory (only if it exists and has files)
+if [[ -d "$CONTRACTS_DIR" ]] && [[ -n "$(ls -A "$CONTRACTS_DIR" 2>/dev/null)" ]]; then
+    docs+=("contracts/")
+fi
+
+[[ -f "$QUICKSTART" ]] && docs+=("quickstart.md")
+
+# Include tasks.md if requested and it exists
+if $INCLUDE_TASKS && [[ -f "$TASKS" ]]; then
+    docs+=("tasks.md")
+fi
+
+# Output results
+if $JSON_MODE; then
+    # Build JSON array of documents
+    if [[ ${#docs[@]} -eq 0 ]]; then
+        json_docs="[]"
+    else
+        json_docs=$(printf '"%s",' "${docs[@]}")
+        json_docs="[${json_docs%,}]"
+    fi
+    
+    printf '{"FEATURE_DIR":"%s","AVAILABLE_DOCS":%s}\n' "$FEATURE_DIR" "$json_docs"
+else
+    # Text output
+    echo "FEATURE_DIR:$FEATURE_DIR"
+    echo "AVAILABLE_DOCS:"
+    
+    # Show status of each potential document
+    check_file "$RESEARCH" "research.md"
+    check_file "$DATA_MODEL" "data-model.md"
+    check_dir "$CONTRACTS_DIR" "contracts/"
+    check_file "$QUICKSTART" "quickstart.md"
+    
+    if $INCLUDE_TASKS; then
+        check_file "$TASKS" "tasks.md"
+    fi
+fi