I Built A Claude Code Skill That Turns Claude Into A Professional Project Architect - Generate Complete Requirements, Design Docs, And Implementation Plans In Minutes (Built With Claude) — Design skill for Claude Code

I built a Claude Code Skill that turns Claude into a professional project architect - Generate complete requirements, design docs, and implementation plans in minutes (Built with Claude)

**Productivity**

Ever start a project and realize 3 days in that you should have planned better? Or tried to get Claude to help build something complex only to watch it lose track halfway through? I just released the **project-planner** skill that solves this by turning Claude into your personal project architect.

Why I built this

I was tired of:

• Starting projects with enthusiasm, then getting lost in complexity
• Claude forgetting context in large projects
• Rewriting the same code because requirements weren't clear
• "Just one more feature" turning into complete refactoring
• Having ideas but not knowing how to structure them properly

So I built a skill that makes Claude generate professional-grade planning documents BEFORE writing a single line of code. The kind of docs that $200/hour consultants charge thousands for.

**GitHub:** [https://github.com/adrianpuiu/claude-skills-marketplace]

Installation (literally 30 seconds):

cd ~/.claude/skills/user
git clone [your-repo-url] project-planner

That's it. Open Claude Code and say "What are my skills?" - it's ready to architect.

How it works - The Magic Triple:

Tell Claude: **"I want to build [your project idea]"**

Claude immediately generates THREE documents that become your project's DNA:

1. Requirements Document

Real user stories with testable acceptance criteria:

User Story: As a trader, I want real-time alerts, so that I never miss opportunities

Acceptance Criteria:
✓ WHEN price crosses threshold, THE system SHALL notify within 100ms
✓ THE system SHALL support 10,000 concurrent alerts
✓ IF connection fails, THEN THE system SHALL queue notifications

2. Technical Design Document

Complete architecture with components, interfaces, and data flow:

Claude → "Here's your 3-tier architecture with microservices..."
Claude → "Component responsibilities mapped..."
Claude → "API contracts defined..."
Claude → "Docker config ready..."

3. Implementation Plan

Hierarchical task breakdown with requirement tracing:

- [x] Phase 1: Infrastructure Setup
  - [x] 1.1 Database schema
    - Requirements: REQ-1.2, REQ-3.4
  - [ ] 1.2 Docker configuration
    - Dependencies: Task 1.1

Real Example That Blew My Mind:

**Me:** "I need an order flow trading automation system"

**Claude** (with project-planner):

1. Generated 15 requirements with 67 acceptance criteria
2. Designed a complete event-driven architecture
3. Created 9 implementation phases with 43 tasks
4. Each task traced back to specific requirements
5. Included WebSocket handlers, risk management, backtesting framework

**Result:** What would have taken me 2 weeks of planning was done in 3 minutes. Then when I said "implement task 1.1", Claude knew EXACTLY what to build because it had the blueprint.