lucasilverentand/create-planner-project
plugins/linear-planner/skills/create-planner-project/SKILL.md
Creates fresh Linear planning projects from Luca's five-phase planner structure. Use when the user asks to "create a planner project", "set up planning in Linear", "turn this app idea into a Linear planning project", or replace a live Linear template project with a reusable skill-backed workflow. Use when a real web, native, backend, automation, data, AI, or mixed-surface project needs initiative, project, milestone, and issue records in Linear without keeping reusable template issues live.
$ install --global
skillsauthnpx skillsauth add lucasilverentand/skills create-planner-projectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 6:46 AM124.7s3 files scanned
SKILL.md
- name:
- create-planner-project
- description:
- Creates fresh Linear planning projects from Luca's five-phase planner structure. Use when the user asks to "create a planner project", "set up planning in Linear", "turn this app idea into a Linear planning project", or replace a live Linear template project with a reusable skill-backed workflow. Use when a real web, native, backend, automation, data, AI, or mixed-surface project needs initiative, project, milestone, and issue records in Linear without keeping reusable template issues live.
Create Planner Project
Use this skill to create a real Linear planning project from a reusable structure. The structure lives in references/planner-project-structure.md; shared issue rules live in ../linear-issues/references/issue-rules.md.
Core rule
Never keep a reusable "Project Planning Template" project alive in Linear. Linear should contain real initiatives, real projects, and real work only. This skill creates fresh project records for a specific app or product area.
Maintenance rule
When changing what this plugin does, how it uses Linear, or how the reusable planner structure works, read ../../documents/project-brief.md first and keep it aligned with the skill and reference changes.
Workflow
- Confirm the project name, Linear team, matching initiative, project type, and intended surfaces. If the initiative does not exist, propose creating it first.
- Read
references/planner-project-structure.mdand../linear-issues/references/issue-rules.mdbefore creating anything. - Choose the closest project type profile from the reference. For mixed products, choose a primary profile and list secondary surfaces in the relevant issue descriptions.
- Create or select one real Linear project under the initiative. Use a name like
<Product> Planningunless the user gives a better name. - Set the project to Planning, add the initiative, set a lead if known, and avoid adding a cycle unless the user explicitly asks for this planning work to be in the current cycle.
- Create the five milestones exactly as listed in the reference.
- Create the 23 issues from the reference. Follow the issue-creation rules for labels, priorities, milestones, parent issues, related issues, blockers, and status updates.
- Leave issues in Todo for committed planning work. Use Suggestion only when the user asked for a speculative draft.
- Add a short project status update explaining that the planner project was created and naming the first unblocked issue.
Field rules
- Do not copy source Linear issue IDs or branch names from the reference.
- Do not assign a cycle by default.
- Do not create implementation issues during setup. This skill creates planning and foundation issues only.
- Do not duplicate Linear relationship rules in packaging-specific prompts. Keep them in
../linear-issues/references/issue-rules.md. - Do not force a web stack onto non-web projects. Use the project type profile to decide which stack, distribution, testing, privacy, and observability criteria apply.
- Keep Linear planning documents as the source of truth until a repository exists. Repo docs should link back to Linear instead of duplicating the whole plan.
- If the user wants to migrate an existing template project, move or recreate the issues under the real project, then recommend archiving the template project.
Follow-up cleanup
After creating a planner project from a former live template, flag these cleanup actions:
- Archive the old template project once its issues are moved or recreated.
- Remove any accidental template issues from active cycles.
- Make sure the initiative itself has at least a summary, owner, and the new planning project attached.
Related Skills
lucasilverentand/foundations
development
VerifiedTrustedCommunity
Cross-platform Apple Human Interface Guidelines: color, typography, layout, materials, motion, accessibility, SF Symbols, branding, plus shared UI elements (activity views, rating indicators, web views, …) and meta sections (components, patterns, technologies). Use when the design topic is platform-agnostic. User says: "iOS color tokens", "SF Symbols", "Apple typography", "dark mode guidance".
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-workflow
development
VerifiedTrustedCommunity
Guides a full system design from idea to spec — sequences requirements gathering, architecture decomposition, data modeling, API design, and document writing into a coherent workflow with clear handoffs. Use when the user asks to "design a system", "build X from scratch", "architect something end-to-end", "plan a new service", or has a broad design ask that spans multiple concerns. Also use when the user says things like "I need to build X" without specifying which aspect to start with. This is the entry point for any design task that isn't clearly scoped to a single skill (data model only, API only, etc.).
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-system
development
VerifiedTrustedCommunity
Synthesizes build-ready design systems and DESIGN.md files from chat briefs, screenshots, moodboards, videos, URLs, live pages, or local image folders while preserving the target product identity. Use when the user asks to "make a design system from these screenshots", "turn this moodboard into DESIGN.md", "extract the design language from this video", "define the UX vibe and rules from these references", or create cohesive UI rules from visual inspiration.
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-review
development
VerifiedTrustedCommunity
Reviews and critiques an existing or proposed system design — flags single points of failure, missing non-functional requirements, scaling bottlenecks, security gaps, operational blind spots, unjustified tech choices, and places where the design will fall over under load or failure. Produces a structured review with severity-tagged findings, not just vibes. Use when the user asks for a second opinion on an architecture, requests a design review, wants feedback on a proposed system, pastes a design doc, or says things like "review this design", "what's wrong with X", "poke holes in this", or "is this a good architecture".
3SKILL.mdUpdated Jun 13, 2026