Reviewing project documentation for feature template

Let me review the documents to understand the project and the task at hand.

From docs/high-level.md, I understand that:

• Petrock is a Go CLI tool for bootstrapping new Go projects and generating files
• It targets web applications using event sourcing
• It generates code templates and overrides files (requiring a clean git state)
• It has two main commands: petrock new <project> and petrock feature <name>
• When generating a feature, it creates a package with various files (commands.go, queries.go, etc.)
• The application follows a specific architecture with command/query handlers, state management, etc.

From docs/plan-feature-template-structure.md, I see a detailed task breakdown for reorganizing the feature template structure:

• The plan is to move from a flat directory structure to a hierarchical one
• This involves creating directories (commands/, handlers/, queries/, etc.)
• Tasks T1-T10 outline the steps to migrate code to the new structure
• Each task has subtasks and a "Definition of Done"
• Overall, the goal is to improve maintainability by distributing functionality across smaller, more focused files

Let me check if I have enough information to execute this plan:

1. I understand the current structure of Petrock feature templates (flat structure with files like commands.go, queries.go, etc.)
2. I understand the target structure (hierarchical with directories for different responsibilities)
3. I have detailed tasks with clear steps for each part of the migration
4. I can see the implementation details and examples for the new structure

What I might need more information about:

1. The location of the internal/skeleton/feature_template directory in the project
2. Access to the current code to understand the specific content that needs to be migrated
3. Details about dependencies between different parts of the code

Let me check if I can find this information using the tools available.

Let's follow the plan step by step. The first task is T1: Create Directory Structure.

According to the plan, I need to:

1. Create directories in internal/skeleton/feature_template/: commands/, handlers/, queries/, state/, ui/, routes/, workers/
2. Add .keep files in each directory to ensure they're tracked by git
3. Create subdirectory structure (ui/components/, ui/layouts/, ui/pages/)

Let's implement T1.1 first and then T1.2.