docs: clarify template initialization scope and prevent TaskMaster auto-setup (#8)

* feat: improve template workflow and README handling

- Clarify GitHub template vs clone workflows in README and rules
- Abstract README template to .cursor/templates/project_readme.md
- Rename preserved README to how_to_use_this_template.md
- Minimize workflow rules by extracting template content
- Better organization and maintainability

* refactor: simplify and improve template workflow

- Remove unnecessary .gitignore creation step (already exists in template)
- Simplify paging prevention to single export PAGER="" command
- Update prompt format to "initialize this project as <my project name>"
- Streamline workflow rules and remove verbose CLI instructions
- More natural and consistent user experience

* refactor: abstract detailed workflow steps to separate files

- Create repository_initialization.mdc with detailed git setup steps
- Create template_setup.mdc with detailed project initialization steps
- Update workflow.mdc to reference abstracted files instead of inline content
- Emphasize mandatory Pull Request step in Branch Protection Workflow
- Reduce context usage while maintaining access to detailed instructions

* docs: clarify template initialization scope and prevent TaskMaster auto-setup

- Add explicit boundaries for template initialization workflow
- Create 'What NOT to Include' section to prevent scope creep
- Emphasize that TaskMaster, PRD creation, and git setup are separate workflows
- Remove automatic TaskMaster setup from template initialization
- Add warning in main workflow.mdc about initialization scope

Author: jpke

.cursor/rules/template_setup.mdc

@@ -6,18 +6,27 @@ alwaysApply: false
 # Template Setup Workflow
 
 ## Agent-Driven Initialization
-When a user prompts "initialize this project as <my project name>", I will automatically handle template setup:
+When a user prompts "initialize this project as <my project name>", I will **ONLY** handle template setup (do NOT include TaskMaster or PRD work):
 
 1. **Copy `.cursor/.mcp.json.example` to `.cursor/mcp.json`** and prompt user for their API keys
-2. **Optionally copy `.env.example` to `.env`** only if they plan to use TaskMaster CLI (not needed for MCP workflow)
-3. **Remove template-specific content** and customize for their project:
+2. **Remove template-specific content** and customize for their project:
    - **Move `README.md` to `docs/how_to_use_this_template.md`** to preserve template documentation
    - **Copy `.cursor/templates/project_readme.md` to the project root as `README.md`** to create the new project-specific README
    - **Update the new `README.md`** by replacing `[Project Name]` placeholder with user-provided name or "My Project"
    - Update `SECURITY.md` to remove template references
    - Remove or update any hardcoded paths in configuration files
 
+## What NOT to Include in Template Initialization
+- **Do NOT set up TaskMaster** - This is a separate workflow that requires explicit user request
+- **Do NOT create PRDs** - Project Requirements Documents are separate from template setup
+- **Do NOT copy `.env.example` to `.env`** - Only do this if user specifically requests TaskMaster CLI setup
+- **Do NOT initialize git repository** - Template initialization is separate from git setup
+- **Do NOT create tasks or project management files** - Focus only on template structure
+
 ## Environment File Distinction
 - **Template `.env.example`**: Contains TaskMaster CLI configuration (ANTHROPIC_API_KEY, PERPLEXITY_API_KEY, etc.)
 - **Project `.env`**: Will contain application-specific configuration (database URLs, app API keys, etc.)
 - **Never mix these**: TaskMaster configuration is separate from project application configuration
+
+## After Template Initialization
+Template initialization is complete after customizing the project files. TaskMaster, PRD creation, and git setup are separate workflows that require explicit user requests.

.cursor/rules/workflow.mdc

@@ -7,6 +7,8 @@ alwaysApply: true
 ## Template Setup Workflow
 For detailed steps on template setup when initializing a project, see [template_setup.mdc](mdc:.cursor/rules/template_setup.mdc).
 
+**IMPORTANT**: Template initialization is ONLY about setting up project structure and configuration. TaskMaster, PRD creation, and git setup are separate workflows that require explicit user requests.
+
 ## MCP Server Workflows
 
 ### Memory MCP