team-shinchan:bigproject
npx machina-cli add skill seokan-jeong/team-shinchan/bigproject --openclawEXECUTE IMMEDIATELY
Output immediately before executing:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🌸 [Himawari] Large-scale project mode engaged! 🚀
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Step 1: Validate Input
If args is empty or only whitespace:
Ask user: "What large-scale project would you like to tackle?"
STOP and wait for user response
If args length > 2000 characters:
Truncate to 2000 characters
Warn user: "Request was truncated to 2000 characters"
Step 2: Evaluate Scope
This skill is for large projects meeting ANY of these criteria:
| Criteria | Threshold |
|---|---|
| Phases | 3+ phases |
| Files | 20+ files affected |
| Domains | 3+ domains (frontend + backend + infra) |
| Duration | Multi-session effort |
If the project doesn't meet these criteria, recommend using /team-shinchan:start instead.
Step 3: Execute Task
Do not read further. Execute this Task NOW:
Task(
subagent_type="team-shinchan:himawari",
model="opus",
prompt=`/team-shinchan:bigproject has been invoked.
## Large-Scale Project Orchestration Request
Manage complex projects including:
| Responsibility | Actions |
|----------------|---------|
| Decomposition | Break into manageable phases |
| Dependencies | Identify cross-cutting concerns |
| Allocation | Assign right agents to tasks |
| Tracking | Monitor overall progress |
| Coordination | Manage specialist teams |
## Project Structure Requirements
1. **Scope Analysis**: Understand full project scope
2. **Phase Planning**: Create logical phases with dependencies
3. **Resource Mapping**: Assign specialists to each phase
4. **Risk Assessment**: Identify potential blockers
5. **Progress Tracking**: Set up monitoring
## Output Format
- Project overview and scope assessment
- Phased implementation plan
- Agent assignments per phase
- Risk mitigation strategy
- Success criteria per phase
User request: ${args || '(Please describe the large-scale project)'}
`
)
STOP HERE. The above Task handles everything.
Source
git clone https://github.com/seokan-jeong/team-shinchan/blob/main/skills/bigproject/SKILL.mdView on GitHub Overview
Orchestrates large, multi-phase initiatives using Himawari to decompose work, map resources, and coordinate specialist teams. It outputs a phased implementation plan with assignments, risk mitigation, and explicit success criteria. It’s designed for projects that meet 3+ phases, 20+ touched files, or 3+ domains across multi-session efforts.
How This Skill Works
On invocation, this skill follows an EXECUTE IMMEDIATELY workflow: it validates input, evaluates the project scope against defined thresholds, and then invokes a Himawari subagent to generate a comprehensive plan. The result includes a project overview, a phased plan, per-phase agent assignments, risk mitigation strategies, and phase-specific success criteria.
When to Use It
- Coordinating a multi-phase overhaul across frontend, backend, and infra.
- A data migration or platform upgrade touching 20+ files.
- A cross-domain initiative requiring 3+ domains and dependency mapping.
- A long-running, multi-session project needing phased milestones.
- Any big initiative that requires resource mapping and a risk-aware execution plan.
Quick Start
- Step 1: Provide the project description (args). If empty, prompt the user for details.
- Step 2: The skill validates input, truncates if over 2000 chars, and assesses scope against 3+ phases, 20+ files, and 3+ domains.
- Step 3: Receive a comprehensive plan with phased milestones, agent assignments per phase, risk mitigation, and success criteria.
Best Practices
- Define clear phase boundaries and dependencies before starting.
- Map resources per phase and document cross-domain constraints.
- Identify blockers early and craft per-phase risk mitigations.
- Set explicit success criteria for each phase and track progress against them.
- Use Himawari to monitor progress and adapt the plan as reality shifts.
Example Use Cases
- Enterprise platform upgrade spanning frontend, API backend, and infrastructure.
- Data migration across 20+ files with a phased rollout across domains.
- Multi-domain SaaS feature launch requiring cross-team alignment.
- Legacy system rewrite executed in 4+ phases with risk planning.
- Global service deployment across regions with phased rollout and coordination.
