analyze-project
Project Analysis
Overview
Perform comprehensive project analysis across three dimensions: Features, Architecture, and Implementation. Provide actionable insights with specific file paths and line references.
Core principle: Read and understand, never modify. Always provide concrete code references.
Announce at start: "I'm analyzing this project's features, architecture, and implementation."
${languageInstruction}
Critical Constraints
- READ-ONLY - Do not edit or create any files
- NO CODE GENERATION - Only reference existing code
- ALWAYS CITE SOURCES - Include
file:linereferences for all code mentions - SAVE REPORT - Save analysis to
docs/analysis/YYYY-MM-DD-<project-name>.md
More from nu1nux/open-skills
spec-write-plan
Write a detailed, step-by-step implementation plan and save it under docs/plans.
7code-review
Review code changes for quality, security, and best practices; save report to docs/reviews/
6spec-save-design
Convert a /spec:brainstorm session into a structured design document saved under docs/designs.
5spec-brainstorm
Lead structured design brainstorming with questions, alternatives, and incremental validation; no code or file edits.
5spec-execute-plan
Review an implementation plan and execute tasks in batches with checkpoints and reporting.
5