Guild-Agents/guild / .claude/skills/re-specialize
re-specialize
VerifiedIncremental re-specialization — re-scans the project and updates only auto-generated zones in CLAUDE.md and agents
Re-Specialize
Incrementally updates auto-generated content in CLAUDE.md and agent files without touching user customizations. Uses protected zone markers to identify what can be safely regenerated.
When to use
- When project dependencies have changed (new framework, updated versions)
- When architecture has evolved (new patterns, restructured folders)
- When agents need refreshed context about the project
- Periodically to keep CLAUDE.md in sync with the actual codebase
Process
Step 1 -- Read current state
Read CLAUDE.md and all agent files in .claude/agents/:
- Identify existing zone markers (
<!-- guild:auto-start:ID -->/<!-- guild:auto-end:ID -->) - Note which zones exist and their current content
- Identify any user customizations outside of zones
Step 2 -- Explore the project
Same exploration as guild-specialize:
- Scan dependency files for current stack and versions
- Analyze project structure and architecture patterns
- Detect code conventions from linter/formatter configs
- Check environment variable examples
Step 3 -- Check zone markers
If CLAUDE.md has zone markers, proceed to regeneration.
If CLAUDE.md does NOT have zone markers (legacy project):
- Offer to inject markers around the auto-generated sections
- Show the user where markers would be placed
- Require explicit confirmation before modifying
- If user declines, abort gracefully
Step 4 -- Regenerate zone content
Invoke the Tech Lead agent using Task tool with model: "opus" (reasoning tier):
- Generate fresh content for each zone based on the project scan
- Compare new content with existing zone content
- Present a diff for each zone to the user
- Only replace zones where content has actually changed
Zones to regenerate:
| Zone ID | Content |
|---|---|
structure | Project folder structure with descriptions |
architecture | Architecture patterns and design decisions |
conventions | Code conventions from linter/formatter |
env-vars | Environment variables from .env.example |
Step 5 -- Update agent context
Invoke the Tech Lead agent using Task tool with model: "sonnet" (execution tier):
- For each agent in
.claude/agents/*.md, update theagent-contextzone - If no
agent-contextzone exists, append one at the bottom - Preserve everything outside the zone (role definition, process, rules)
Step 6 -- Confirm changes
Present a summary:
Re-specialization complete for [project-name]
Zones updated:
- structure: [changed/unchanged]
- architecture: [changed/unchanged]
- conventions: [changed/unchanged]
- env-vars: [changed/unchanged]
Agents updated: [count] of [total]
Review the changes above. Confirm to commit.
Step 7 -- Commit
Commit all changes as an atomic commit:
git add CLAUDE.md .claude/agents/*.md
git commit -m "chore: re-specialize via guild-re-specialize"
Important Notes
- NEVER modify content outside of zone markers
- NEVER read real
.envfiles -- only.env.example - If a zone's content hasn't changed, skip it (no-op)
- Present diffs before applying changes
- User confirmation is required before committing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |