Template

Files

Paul.Kim c9020eb796 docs: 초기 파일 추가 및 기본 설정 구성

- .git-commit-template.txt: 커밋 메시지 템플릿 추가
- .gitignore: OS 및 데이터베이스 관련 파일 무시 설정 추가
- .mcp.json: MCP 서버 설정 추가
- CLAUDE.md: SuperClaude 엔트리 포인트 문서 추가
- README.md: 프로젝트 템플릿 설명 추가
- .claude/COMMANDS.md: 명령어 실행 프레임워크 문서 추가
- .claude/FLAGS.md: 플래그 시스템 문서 추가
- .claude/MCP.md: MCP 서버 통합 문서 추가
- .claude/MODES.md: 운영 모드 문서 추가
- .claude/ORCHESTRATOR.md: 지능형 라우팅 시스템 문서 추가
- .claude/PERSONAS.md: 페르소나 시스템 문서 추가
- .claude/PRINCIPLES.md: 핵심 원칙 문서 추가
- .claude/RULES.md: 실행 가능한 규칙 문서 추가
- .claude/settings.json: 권한 설정 추가
- .claude/commands 디렉토리: 다양한 명령어 문서 추가
- .taskmaster/config.json: 기본 설정 파일 추가
- .taskmaster/docs 디렉토리: 문서 파일 추가
- .taskmaster/tasks/tasks.json: 기본 작업 파일 추가

2025-07-20 22:25:33 +09:00

1.8 KiB

Raw Blame History

allowed-tools, description

allowed-tools	description
mcp__taskmaster-ai__update, mcp__taskmaster-ai__update_task, mcp__taskmaster-ai__update_subtask, mcp__taskmaster-ai__get_tasks	Update tasks interactively with clarifying questions

Update Tasks Interactively

Context

User Request: $ARGUMENTS
Current Tag: !jq -r '.currentTag // "master"' .taskmaster/state.json 2>/dev/null || echo "master"

Goal

Update tasks based on implementation changes by asking clarifying questions to ensure accurate updates.

Process

Analyze Change: Think deeply about the implications of the change.
Ask Clarifying Questions:
- Ask 4-6 targeted questions about the change
- Provide lettered/numbered options for easy response
- Focus on understanding impact and scope
Update Tasks:
- Update affected tasks based on answers
- Show what was changed

Clarifying Questions Framework

Adapt questions based on the change described above. Consider these areas:

Scope: "Which tasks are affected by this change?"
Reason: "Why was this change made?"
Impact: "How does this affect the implementation approach?"
Dependencies: "Does this change affect task dependencies?"
Testing: "How should test strategies be updated?"
Documentation: "What additional context should be added?"

Final Instructions

Think deeply about the change and its implications
Ask clarifying questions with lettered/numbered options
Update tasks based on the answers
Confirm what was updated

Example Usage

/project:task:update-interactive switching to microservices architecture

This will:

Ask about which components are affected
Understand the migration approach
Update relevant tasks with new architecture details

1.8 KiB Raw Blame History