Skip to content

Comments

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

Merged
jpke merged 6 commits intomainfrom
feature/template-workflow-improvements
Jul 4, 2025
Merged

docs: clarify template initialization scope and prevent TaskMaster auto-setup#8
jpke merged 6 commits intomainfrom
feature/template-workflow-improvements

Conversation

@jpke
Copy link
Owner

@jpke jpke commented Jul 4, 2025

This PR adds important clarifications to the template initialization workflow to prevent agents from automatically including TaskMaster setup when users just want to initialize a project template.

Problem

Agents were conflating template initialization with TaskMaster workflow setup, automatically including:

  • TaskMaster setup
  • PRD creation
  • Git repository initialization
  • Task management files

Solution

Added explicit boundaries and a "What NOT to Include" section to clarify that template initialization should ONLY handle:

  • Project structure setup
  • Configuration file customization
  • Template-specific content removal

Changes Made

  • Added explicit scope limitation: Template initialization will ONLY handle template setup
  • Created "What NOT to Include" section with clear boundaries:
    • Do NOT set up TaskMaster
    • Do NOT create PRDs
    • Do NOT copy .env.example to .env (unless explicitly requested)
    • Do NOT initialize git repository
    • Do NOT create tasks or project management files
  • Added prominent warning in main workflow.mdc about initialization scope
  • Reinforced separation between template setup and other workflows

Impact

Now when an agent is prompted to "initialize this project as Calendar App", it will focus only on template customization and won't automatically include project management tooling setup.

jpke added 6 commits July 4, 2025 16:58
- 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
- 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
- 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
…to-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
@jpke jpke merged commit 55cab60 into main Jul 4, 2025
@jpke jpke deleted the feature/template-workflow-improvements branch July 4, 2025 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant