From solo
This skill should be used when the user asks to 'project tracking', 'manage project', or 'project status'.
npx claudepluginhub jamon8888/cc-suite --plugin SoloThis skill uses the workspace's default tool permissions.
Lightweight, file-based project tracking for solopreneurs. Each project lives in `data/1-Projets/[project-name]/README.md` using a standardized template. Primary skill for the `/solo:plan project` command.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
Lightweight, file-based project tracking for solopreneurs. Each project lives in data/1-Projets/[project-name]/README.md using a standardized template. Primary skill for the /solo:plan project command.
Create a new project from references/project-template.md:
proposal-generator) or ask user to list themdata/1-Projets/[project-name]/references/project-template.md β data/1-Projets/[project-name]/README.mddata/1-Projets/clients/[client].md to this projectEach project has 3-5 milestones with target dates and status:
| Status | Meaning | Visual |
|---|---|---|
| Not Started | Work hasn't begun | β¬ |
| In Progress | Actively working on it | π‘ |
| Completed | Delivered and accepted | β |
| Overdue | Past target date, not complete | π΄ |
| Blocked | Can't proceed (reason in notes) | β |
Deliverables use a checkbox format with assignee and due date:
- [ ] Deliverable description β Due: [date]
- [x] Completed deliverable β Done: [date]
Generate a status summary on demand:
## [Project Name] β Status: [On Track / At Risk / Overdue]
- **Progress:** [X/Y] milestones complete, [A/B] deliverables done
- **Next milestone:** [Name] β due [date] ([X] days away)
- **Blockers:** [None / list]
- **Hours logged:** [X] / [Y] estimated
When checking project status, flag items as overdue:
| Check | Condition | Action |
|---|---|---|
| Milestone overdue | Target date < today AND status β Completed | Mark π΄, add to weekly review |
| Deliverable overdue | Due date < today AND not checked | Highlight in status report |
| Project overdue | End date < today AND status β TerminΓ© | Escalate: suggest client communication |
| Stale project | No updates in 14+ days | Flag during weekly review |
When a milestone is overdue, provide this communication template:
Hi [Client Name],
Quick update on [Project Name]. The [Milestone] milestone was originally targeted for [date]. We're currently [X days] past that due to [reason β e.g., "waiting on content from your team" / "the scope addition we discussed last week"].
Updated timeline: I expect to complete this by [new date]. Impact on final delivery: [None / Pushes final delivery to [date]].
Let me know if you'd like to discuss any adjustments.
For deliverables that require client sign-off:
Mark deliverable as "Submitted" in project file. Send to client with:
"Please review [deliverable] and let me know if it meets your expectations. I'll consider it approved if I don't hear back within [3 business days]."
| Status | Meaning |
|---|---|
| Submitted | Sent to client, awaiting review |
| Approved | Client confirmed acceptance |
| Revision Requested | Client wants changes (track as revision round) |
| Auto-Approved | No response within review window |
scope-managementUpdate the deliverable with approval date. This triggers:
invoice-generatorWhen running multiple projects, generate an overview:
## Active Projects β [Date]
| Project | Client | Status | Next Milestone | Due | Health |
|---------|--------|--------|---------------|-----|--------|
| [Name] | [Client] | On Track | [Milestone] | [Date] | π’ |
| [Name] | [Client] | At Risk | [Milestone] | [Date] | π‘ |
| [Name] | [Client] | Overdue | [Milestone] | [Date] | π΄ |
**Overdue items:** [count]
**Pending approvals:** [count]
**This week's deadlines:** [list]
proposal-generator deliverablesclient-management cardsweekly-reviewscope-management scriptsinvoice-generator (milestone billing)~~project tracker is connected, sync milestones and deliverables with the external toolreferences/project-template.md: Standard markdown structure for new projects