writing-plans
Generate detailed implementation plans for multi-step coding tasks
Também disponível em: Cycleaddict,obra,ZhanlinCui,DYAI2025,davila7,DMJGilbert,Cygnusfear,CodingCossack
Transform specifications into actionable implementation plans with granular tasks. This skill bridges the gap between requirements and code by creating comprehensive documentation that assumes zero prior context.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "writing-plans". Create a plan for adding password reset functionality
Resultado esperado:
- # Password Reset Implementation Plan
- **Goal:** Allow users to reset passwords via email link
- **Architecture:** Token-based reset flow with expiration, using existing email service
- **Tech Stack:** Node.js, PostgreSQL, Nodemailer
- ---
- ### Task 1: Database Schema
- **Files:**
- - Modify: `migrations/001_add_password_reset.sql`
- **Step 1: Create migration file**
- ```sql
- ALTER TABLE users ADD COLUMN password_reset_token TEXT;
- ALTER TABLE users ADD COLUMN password_reset_expires TIMESTAMP;
- ```
- **Step 2: Run migration**
- Run: `npm run migrate`
- Expected: 'Migration successful'
A utilizar "writing-plans". Plan the implementation of a REST API endpoint
Resultado esperado:
- ### Task 3: Create API Endpoint
- **Files:**
- - Create: `src/api/users.ts`
- - Test: `tests/api/users.test.ts`
- **Step 1: Write the failing test**
- ```typescript
- describe('GET /api/users/:id', () => {
- it('returns user by id', async () => {
- const response = await request(app).get('/api/users/1');
- expect(response.status).toBe(200);
- expect(response.body.name).toBe('Test User');
- });
- });
- ```
- **Step 2: Run test to verify it fails**
- Run: `npm test -- tests/api/users.test.ts`
- Expected: FAIL with 'Cannot GET /api/users/1'
Auditoria de Segurança
SeguroStatic analysis detected 20 potential issues (16 external command patterns, 4 weak cryptography flags). All are false positives from markdown code spans and code blocks in documentation. This is a documentation-only skill with no executable code, network operations, or security risks. Safe to publish.
Pontuação de qualidade
O Que Você Pode Construir
Onboarding new developers
Create detailed plans that help developers unfamiliar with your codebase implement features correctly without requiring constant supervision
Complex feature implementation
Break down multi-step features into manageable tasks with clear testing and verification steps for systematic development
Test-driven development workflows
Generate TDD task sequences that guide developers through writing tests first, implementing code, and verifying functionality
Tente Estes Prompts
Create an implementation plan for adding user authentication to our web application. Use the writing-plans skill to break this down into bite-sized tasks.
Use writing-plans to create a detailed plan for refactoring the payment processing module. Include tests, file changes, and migration steps.
I need to integrate the Stripe API for subscription management. Use writing-plans to create a complete implementation plan with all necessary steps.
Create an implementation plan for our real-time notification system that includes database changes, API endpoints, background workers, and frontend components.
Melhores Práticas
- Always start with the required plan header including goal, architecture, and tech stack to provide complete context
- Break tasks into the smallest possible units (2-5 minutes each) so developers can make steady progress with frequent commits
- Include exact file paths and complete code examples in plans to eliminate ambiguity and decision-making during implementation
- Specify expected test output at each step so developers can verify their work before proceeding
Evitar
- Writing vague instructions like 'add validation' or 'update the handler' without specifying exact code and file locations
- Creating large tasks that combine multiple steps, which makes progress tracking and error isolation difficult
- Skipping test cases or expected outputs, which forces developers to guess what success looks like
- Omitting the plan header or context sections, assuming the implementer has background knowledge