Skip to content
Back to search

claude-skills-marketplace

MarketplaceWorks with Claude CodeGitHub

A comprehensive skill that establishes Claude as a Project Architect to generate detailed planning documents that serve as blueprints for AI-assisted software development.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/adrianpuiu--claude-skills-marketplace/badge.svg)](/listings/adrianpuiu--claude-skills-marketplace)

HTML

<a href="/listings/adrianpuiu--claude-skills-marketplace"><img src="/api/listings/adrianpuiu--claude-skills-marketplace/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude install

/plugin marketplace add adrianpuiu/claude-skills-marketplace

/plugin install project-planner-skill@claude-skills-marketplace

Chinese users can also discover more skills through Skills宝: https://skilery.com

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 27 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "claude-skills-marketplace",
  3. "id": "claude-skills-marketplace",
  4. "owner": {
  5. "name": "George A Puiu",
  6. "email": "puiu.adrian@gmail.com"
  7. },
  8. "metadata": {
  9. "description": "Claude Skills Marketplace - A centralized repository for Claude Code skills and plugins",
  10. "version": "1.0.0"
  11. },
  12. "plugins": [
  13. {
  14. "name": "project-planner-skill",
  15. "source": "./project-planner-skill",
  16. "description": "Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking.",
  17. "version": "1.0.0",
  18. "author": {
  19. "name": "George A Puiu",
  20. "email": "puiu.adrian@gmail.com"
  21. },
  22. "keywords": ["project-planning", "documentation", "requirements", "design", "implementation"],
  23. "category": "productivity",
  24. "strict": false
  25. }
  26. ]
  27. }
README.md · README · 140 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # FYI : I suggest you to check this repository for spec docs on steroids skill-> https://github.com/adrianpuiu/specification-document-generator
  2. #
  3. # Project Planner Skill - will be deleted , it's obsolete and will be replaced by -> https://github.com/adrianpuiu/specification-document-generator
  4. A comprehensive skill that establishes Claude as a **Project Architect** to generate detailed planning documents that serve as blueprints for AI-assisted software development.
  5. ## What This Skill Does
  6. This skill transforms Claude into a System Architect who creates comprehensive project documentation by:
  7. 1. **Defining the complete system architecture upfront** - All components, data flows, and integration points
  8. 2. **Setting clear project boundaries** - What's in scope, out of scope, and key constraints
  9. 3. **Creating traceable documentation** - Requirements → Design → Implementation tasks
  10. The skill generates three essential documents:
  11. 1. **Requirements Document** - User stories with testable acceptance criteria and traceable IDs
  12. 2. **Design Document** - Complete system architecture with component maps, data flows, and integration specifications
  13. 3. **Implementation Plan** - Hierarchical task breakdown with requirement tracing and clear deliverables
  14. ## The Architect Approach
  15. **Why it works:** Setting clear roles, responsibilities, and deliverables upfront dramatically improves output quality. By explicitly defining system components, data flows, and integration points before diving into details, the documentation becomes comprehensive and actionable.
  16. ## Quick Start
  17. ### Claude install
  18. ```bash
  19. /plugin marketplace add adrianpuiu/claude-skills-marketplace
  20. /plugin install project-planner-skill@claude-skills-marketplace
  21. ```
  22. Chinese users can also discover more skills through Skills宝: https://skilery.com
  23. ## Document Types
  24. ### Requirements Document
  25. - User stories in standard format
  26. - Testable acceptance criteria using SHALL statements
  27. - Requirement numbering for traceability
  28. - Glossary of domain terms
  29. ### Design Document
  30. - System architecture diagrams
  31. - Component responsibilities and interfaces
  32. - Data models and schemas
  33. - Error handling strategies
  34. - Deployment configuration
  35. ### Implementation Plan
  36. - Hierarchical task breakdown
  37. - Requirement tracing (links tasks to requirements)
  38. - Dependency management between tasks
  39. - Progress tracking with checkboxes
  40. ## Project Types Supported
  41. - **web-app**: Full-stack web applications
  42. - **cli-tool**: Command-line tools and utilities
  43. - **api-service**: REST/GraphQL API services
  44. - **generic**: General purpose projects
  45. ## Files Included
  46. ### Scripts
  47. - `generate_project_docs.py` - Automated document generation
  48. - `validate_documents.py` - Document validation and completeness checking
  49. ### References
  50. - `domain-templates.md` - Domain-specific templates and patterns
  51. ### Assets
  52. - `requirements-template.md` - Basic requirements document template
  53. ## Best Practices
  54. 1. **Start with Requirements** - Define what the system should do before how
  55. 2. **Be Specific** - Use measurable criteria (e.g., "within 100ms" not "fast")
  56. 3. **Trace Requirements** - Link every task back to requirements
  57. 4. **Include Non-Functional Requirements** - Performance, security, scalability
  58. 5. **Define Clear Interfaces** - Specify how components interact
  59. 6. **Plan Incrementally** - Break large tasks into smaller, manageable pieces
  60. ## Common Use Cases
  61. ### Starting a New Project
  62. ```
  63. User: "I want to build a real-time chat application"
  64. AI: [Uses this skill to generate complete project documentation]
  65. ```
  66. ### Expanding Existing Project
  67. ```
  68. User: "Add user authentication to my project requirements"
  69. AI: [Adds properly formatted requirements with acceptance criteria]
  70. ```
  71. ### Creating Technical Specification
  72. ```
  73. User: "Design the architecture for a microservices e-commerce platform"
  74. AI: [Generates design document with components, interfaces, and deployment]
  75. ```
  76. ## Tips for AI Implementation
  77. When using these documents for AI-assisted development:
  78. 1. **Requirements First** - Implement in order of requirement priority
  79. 2. **Follow Task Dependencies** - Complete prerequisite tasks first
  80. 3. **Test Against Acceptance Criteria** - Each SHALL statement is a test case
  81. 4. **Reference Design Interfaces** - Use the specified APIs and data models
  82. 5. **Track Progress** - Check off completed tasks in the implementation plan
  83. ## Validation Checklist
  84. Before using documents for implementation:
  85. - [ ] All placeholders ([PLACEHOLDER]) filled in
  86. - [ ] Requirements have testable acceptance criteria
  87. - [ ] Design includes all major components
  88. - [ ] Tasks reference requirement IDs
  89. - [ ] Dependencies between tasks identified
  90. - [ ] Non-functional requirements specified
  91. - [ ] Deployment configuration included
  92. ## Example Output
  93. The generated documents follow industry-standard formats that are:
  94. - **Machine-readable** - Structured for AI parsing
  95. - **Human-readable** - Clear for developers to understand
  96. - **Version-control friendly** - Plain text Markdown format
  97. - **Traceable** - Requirements linked through all documents
  98. This skill transforms high-level project ideas into actionable specifications that AI agents can use to build working software.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.