From tycono
Provides Tycono AI team orchestration guide: waves, agencies, roles, /tycono commands, status checks, viewing activity logs in .tycono/activity-streams.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tycono:getting-startedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping a user understand how to use the Tycono AI team orchestration plugin.
You are helping a user understand how to use the Tycono AI team orchestration plugin.
Wave = A task you give to the AI team. Like a sprint. Agency = A team configuration (which roles, what domain knowledge). Role = A specialized AI agent (CTO, Engineer, QA, etc.)
/tycono "your task"
→ CEO Supervisor analyzes task
→ Dispatches roles (CTO, Engineer, QA, etc.)
→ Each role works as a separate Claude session
→ Real-time notifications in your session
→ Results delivered
During the wave:
/tycono:tycono-status for current stateAfter the wave:
.tycono/activity-streams/ses-*.jsonlcat .tycono/activity-streams/ses-cto-*.jsonl | python3 -m json.toolgrep '"type":"text"' .tycono/activity-streams/ses-critic-*.jsonlIf user has an existing project with code/knowledge:
/tycono:agency-create
This scans the project, suggests a team, and auto-generates + auto-verifies.
"How do I see what Critic said?"
→ cat .tycono/activity-streams/ses-critic-*.jsonl | grep '"type":"text"'
"How do I give a follow-up directive?"
→ Just run /tycono "follow-up task" — it creates a new wave in the same project context.
"The team did too much / too little" → Be more specific in the directive. Include what's already done, what the actual problem is, and what you expect.
"How do I set a default agency?"
→ Add to .tycono/config.json: { "defaultAgency": "your-agency-id" }
npx claudepluginhub seongsu-kang/tycono --plugin tyconoCreates and manages dynamic teams of domain-specific agents. Analyzes project to propose 5-20 agents with tracking framework. Modes: create, update, status, cleanup.
Sets up multi-agent teams for complex projects with file-based planning, per-agent directories, and teammate spawning. Triggers on team/swarm/start-project requests.
Returns the universal governance specification for swarm workflow commands: hard rules, briefing templates, launch mechanics, and pulse setup. Useful when a user-authored shortcut command needs the full spec.