@fermindi/pwn-cli 0.5.0 → 0.7.0

package/templates/workspace/.ai/tasks/backlog.md

@@ -1,95 +0,0 @@
-# Backlog
-
-This file contains prioritized future tasks not yet in active work.
-
-## Format
-
-Tasks are listed in priority order (highest to lowest):
-
-```markdown
-### US-XXX: Task Title
-**Type:** Story | Bug | DevTask
-**Priority:** High | Medium | Low
-**Effort:** (T-shirt size: XS, S, M, L, XL)
-**Description:** What needs to be done
-**Acceptance Criteria:**
-- [ ] Criterion 1
-- [ ] Criterion 2
-**Dependencies:** (Other tasks needed first)
-**Notes:** Context, caveats, research needed
-```
-
----
-
-## Moving to Active
-
-When starting a backlog task:
-
-1. Create issue/ticket in your tracking system
-2. Move to `active.md` with checkbox
-3. Assign team member
-4. Update priority based on sprint plan
-5. Reference in commit messages
-
----
-
-## Adding New Tasks
-
-When new work is identified:
-
-1. Assign next ID (US-XXX, BUG-XXX, etc.)
-2. Add to appropriate section
-3. Fill in all fields
-4. Don't assign yet - wait for planning
-5. Commit with message: `docs: add [ID] to backlog`
-
----
-
-## Backlog Sections
-
-### High Priority
-Work that should start soon. Review weekly.
-
-### Medium Priority
-Important but can wait. Review biweekly.
-
-### Low Priority
-Nice-to-have improvements. Review monthly.
-
-### Roadmap (Future Phases)
-Longer-term projects for future planning.
-
----
-
-## Template for New Backlog Item
-
-```markdown
-### US-XXX: [Title]
-**Type:** Story | Bug | DevTask
-**Priority:** High | Medium | Low
-**Effort:** S/M/L
-**Description:** (What and why)
-**Acceptance Criteria:**
-- [ ] (Specific, measurable outcome)
-**Dependencies:** (Other tasks)
-**Notes:** (Research, concerns, constraints)
-```
-
----
-
-## Management Guidelines
-
-- Groom backlog every sprint (remove duplicates, clarify)
-- Estimate effort using relative sizing (XS, S, M, L, XL)
-- Link related tasks together
-- Archive completed items with date + time spent
-- Keep description brief - link to external tickets for details
-
----
-
-## Cleanup
-
-- Remove or update duplicates
-- Close blocked items after 30 days of no progress
-- Archive completed items to `completed/` section
-- Re-estimate if context changes significantly

package/templates/workspace/.claude/commands/mode.md

@@ -1,103 +0,0 @@
-# /mode - PWN Session Mode
-
-Switch between interactive and batch modes, and configure batch execution settings.
-
-## Usage
-
-```
-/mode                     Show current mode and batch config
-/mode interactive         Switch to interactive mode
-/mode batch               Switch to batch mode
-/mode batch [options]     Switch to batch with config changes
-```
-
-## Options (batch mode only)
-
-| Option | Description |
-|--------|-------------|
-| `--max-tasks=N` | Maximum tasks per batch (default: 5) |
-| `--max-hours=N` | Maximum duration in hours (default: 4) |
-| `--quality-gates=X,Y,Z` | Quality gates to run (default: typecheck,lint,test) |
-| `--auto-commit` | Enable auto commit (default) |
-| `--no-auto-commit` | Disable auto commit |
-| `--auto-push` | Enable auto push to remote |
-| `--no-auto-push` | Disable auto push (default) |
-| `--create-pr` | Enable PR creation |
-| `--no-create-pr` | Disable PR creation (default) |
-| `--reset` | Reset config to defaults |
-
----
-
-## Instructions
-
-Run the `pwn mode` CLI command with the user's arguments:
-
-```bash
-pwn mode $ARGUMENTS
-```
-
-If no arguments provided, run:
-
-```bash
-pwn mode
-```
-
-### Examples
-
-Show current mode:
-```bash
-pwn mode
-```
-
-Switch to batch:
-```bash
-pwn mode batch
-```
-
-Configure batch with options:
-```bash
-pwn mode batch --max-tasks=3 --auto-push
-```
-
-Switch to interactive:
-```bash
-pwn mode interactive
-```
-
----
-
-## Modes Explained
-
-### Interactive Mode (default)
-
-- Claude responds to user requests conversationally
-- Asks clarifying questions when needed
-- Commits require explicit user approval
-- Good for exploratory work and collaboration
-
-### Batch Mode
-
-- Claude executes tasks autonomously from backlog
-- Creates feature branches per task
-- Runs quality gates before committing
-- Continues until backlog empty or limits reached
-- Good for repetitive tasks and overnight execution
-
----
-
-## After Running
-
-After executing the command, explain to the user:
-
-1. **Current mode** - What mode they're now in
-2. **Batch config** - Current batch settings (if relevant)
-3. **Next steps** - What they can do next
-
-For batch mode, remind them:
-- Add tasks to `.ai/tasks/backlog.md`
-- Run `pwn batch` to start executing tasks
-- Use `pwn batch status` to check progress
-
-For interactive mode, remind them:
-- Work proceeds conversationally
-- Use `/save` to persist session state

package/templates/workspace/.claude/settings.json

@@ -1,15 +0,0 @@
-{
-  "hooks": {
-    "Notification": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "pwn notify send \"Claude Code aguardando permissao\" --title \"PWN\""
-          }
-        ]
-      }
-    ]
-  }
-}