Uctm Init

What Is Uctm Init?

Uctm Init is a specialized initialization skill designed for the uc-taskmanager (uctm) pipeline within Claude Code environments. It streamlines the setup process for projects that utilize uc-taskmanager by automating workspace directory creation and configuring the necessary Bash permissions in the .claude/settings.local.json file. By invoking this skill, teams and individual developers can rapidly prepare their project for advanced task automation, ensuring the essential infrastructure and security permissions are in place from the outset.

Why Use Uctm Init?

Manual configuration of the uc-taskmanager environment can be repetitive, error-prone, and time-consuming—especially across multiple projects or for new contributors. Uctm Init eliminates this overhead by:

• Automating Directory Setup: Ensures the works/ directory, which is fundamental for uc-taskmanager operations, is always present.
• Standardizing Permissions: Guarantees that essential Bash and file access permissions are correctly set, minimizing runtime issues caused by missing permissions.
• Reducing Onboarding Friction: New team members or automated agents can begin task management immediately, without deep knowledge of the environment setup.
• Improving Security and Consistency: By explicitly managing permissions, uctm-init helps maintain project security and consistent environments across different machines and users.

How to Get Started

Using Uctm Init is straightforward and requires minimal intervention. The skill reacts to commands such as “uctm init”, “initialize uctm”. Here is a practical workflow:

1. Invoke Uctm Init In your Claude Code environment, run or say the initialization command:

uctm init

2. Directory Creation Uctm Init checks if the works/ directory exists in your project root. If not, it creates the directory and reports:

works/ directory created

If the directory already exists, it will notify:

- works/ already exists

3. Permission Configuration Uctm Init will prompt you:

Shall we automatically set the required Bash permissions in .claude/settings.local.json for the agent? (recommended) [Y/n]

Translation: "Shall we automatically set the required Bash permissions in .claude/settings.local.json for the agent? (recommended) [Y/n]"

If you respond with “Y”, “yes”, or equivalent approval:

• .claude/settings.local.json is read or created if missing.
• A predefined list of permissions is merged into the permissions.allow array, skipping any duplicates.

Example of Permission Merge:

Suppose your .claude/settings.local.json initially contains:

{
 "permissions": {
 "allow": ["Read(/**)"]
 }
}

After running Uctm Init and approving, it will update as follows (partial example for brevity):

{
 "permissions": {
 "allow": [
 "Read(/**)",
 "Edit(/**)",
 "Write(/**)",
 "Bash(ls:*)",
 // ... more entries
 ]
 }
}

No permissions already present will be duplicated.

Key Features

• Automatic works/ Directory Creation Ensures the uc-taskmanager workspace is present. If the directory already exists, Uctm Init leaves it untouched, preserving existing files.

• Idempotent Permission Management Efficiently merges a comprehensive set of Bash and file operation permissions into .claude/settings.local.json, skipping existing entries to avoid redundancy.

• Interactive User Consent Before modifying permissions, Uctm Init explicitly seeks user approval, supporting safe and transparent configuration changes.

• Localization Support Recognizes both English and Korean initialization commands and prompts, facilitating international team workflows.

• Seamless Integration Designed to fit Claude Code and its ecosystem, supporting rapid integration with uc-taskmanager plugins and agents.

Best Practices

• Always Run Uctm Init on New Projects Execute Uctm Init immediately after creating a new project repository or cloning an existing one to ensure consistent baseline configuration.

• Review Permissions Regularly Periodically audit the permissions.allow array in .claude/settings.local.json to ensure only necessary permissions are granted, in line with the principle of least privilege.

• Automate as Part of Onboarding Integrate Uctm Init into onboarding scripts or documentation for new contributors to minimize setup errors and ensure uniformity across environments.

• Leverage Version Control Wisely While .claude/settings.local.json is often local and untracked, consider documenting its expected structure in your repository’s onboarding guides.

Important Notes

• No Destructive Actions Uctm Init will not overwrite or remove existing directories or permissions. Its operations are additive and idempotent.

• User Consent is Required Permission changes are only applied after explicit user approval, reducing the risk of accidental over-permissioning.

• Project-Specific Configuration The .claude/settings.local.json file is project-specific. Running Uctm Init in one project does not affect others.

• Manual Customization Remains Possible After initialization, you may further customize permissions as needed. Uctm Init provides a robust default baseline for uc-taskmanager operations.

• Security Implications The permissions list includes powerful Bash commands. Only approve the default set if you trust the agents and scripts that will execute within your project environment.

By incorporating Uctm Init into your project workflow, you ensure a reliable, secure, and consistent foundation for uc-taskmanager-powered automation and productivity enhancements in Claude Code environments.