Back to list
doanchienthangdev

writing-plans

by doanchienthangdev

Omega Vibecode Kit

2🍴 1📅 Jan 21, 2026

SKILL.md


name: writing-plans description: AI agent creates structured implementation plans with task breakdown, dependency mapping, risk assessment, and file-level detail. Use when planning features, projects, or complex implementations.

Writing Plans

Quick Start

  1. Summarize - Executive summary with goals, non-goals, background
  2. Design - High-level approach, architecture diagram, key decisions
  3. Break Down - Tasks in 2-4 hour chunks with file locations
  4. Map Dependencies - Identify critical path and parallel opportunities
  5. Assess Risks - Likelihood x Impact matrix with mitigations
  6. Estimate - Three-point estimation with buffers

Features

FeatureDescriptionGuide
Plan StructureComprehensive templateSummary, design, tasks, testing, risks
Task BreakdownManageable work units2-4 hours, single owner, clear criteria
Dependency MappingSequence and parallelizeCritical path, hard/soft dependencies
Risk AssessmentAnticipate problemsLikelihood x Impact matrix
Effort EstimationRealistic timingThree-point: (O + 4M + P) / 6
File-Level DetailExact code locationsNew files, modifications, line numbers

Common Patterns

# Plan Structure
# Plan: [Feature Name]

## Metadata
- Status: Draft | Approved | In Progress
- Estimated Duration: [X days]
- Priority: P0 | P1 | P2

## Goals & Non-Goals
Goals: [What this WILL accomplish]
Non-Goals: [What this will NOT address]

## Design Overview
[High-level approach, architecture diagram]

## Implementation Tasks

### Phase 1: [Foundation] - [X days]
#### Task 1.1: [Name]
- Description: [What]
- Estimate: [X hours]
- Files: `src/file.ts:45-60`
- Dependencies: None
- Acceptance Criteria:
  - [ ] [Criterion 1]
  - [ ] [Criterion 2]

## Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk] | High | High | [Strategy] |
# Dependency Diagram
           [START]
              |
   +----------+----------+
   |          |          |
[Task 1]  [Task 2]  [Task 3]  <- Parallel
   |          |          |
   +-----+----+          |
         |               |
      [Task 4]      [Task 5]
         |               |
         +-------+-------+
                 |
            [Task 6]      <- Integration
                 |
            [COMPLETE]

Critical Path: 1 -> 4 -> 6 (determines min duration)
# Effort Estimation
Three-Point: (Optimistic + 4*MostLikely + Pessimistic) / 6

Example - OAuth Implementation:
- Optimistic: 4 hours (works first try)
- Most Likely: 8 hours (normal dev)
- Pessimistic: 16 hours (issues)
Estimate = (4 + 32 + 16) / 6 = 8.7 hours

Buffers:
- Individual tasks: 20%
- Phase total: 30%
- Project total: 40%

Best Practices

DoAvoid
Keep tasks to 2-4 hour chunksVague tasks ("implement feature")
Include exact file locationsSkipping background/context
Specify clear acceptance criteriaIgnoring non-functional requirements
Map dependencies explicitlyUnderestimating integration work
Build in buffer for unknownsPlanning more than 2 weeks in detail
Include testing in the planHiding risks or uncertainties
Review plan with stakeholdersAssuming requirements are complete
Update plan as you learnForgetting rollback plans
  • executing-plans - Follow plans systematically
  • thinking-sequentially - Structure reasoning for plans
  • brainstorming-ideas - Generate options for plans
  • verifying-before-completion - Validate plan completion

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon