القائمة
Generate technical plans from specifications. Use when creating architecture documents, designing system components, or preparing for implementation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Execute planned implementations following todo-lists systematically. Use for code generation, building features, and executing SDD plans.
Recall and persist durable project knowledge (decisions, conventions, gotchas, architecture) across SDD sessions. Provider-aware — supports standard (rules-only), Cursor native Memories, and mem0. Use at the start of planning/implementation to recall context, and at the end to persist discoveries.
Update specifications with discoveries made during development. Use when implementation reveals new requirements, constraints, or design changes.
Pattern investigation and technical research before specification. Use when technical approach is unclear, exploring existing solutions, or analyzing codebase patterns. Supports deep research mode for thorough external investigation.
Compare implementation against specifications, identify gaps and issues. Use for code review, quality assurance, and verifying spec compliance.
| name | sdd-planning |
| description | Generate technical plans from specifications. Use when creating architecture documents, designing system components, or preparing for implementation. |
Transform specifications into actionable technical plans.
Read spec.md, note functional/non-functional requirements, review research findings.
Identify components, define responsibilities, design interfaces, plan data flow.
Evaluate against requirements, consider existing stack, document rationale.
Break into phases (Setup → Core → Integration → Polish), identify dependencies, estimate effort.
Identify technical risks, plan mitigations, note assumptions.
Generate plan.md with:
# Technical Plan: [Task ID]
## Overview
## Architecture (Mermaid diagram)
## Components (table: name, responsibility, dependencies)
## Technology Stack (with rationale)
## API Design
## Data Models
## Security Considerations
## Performance Targets
## Implementation Phases (Setup → Core → Integration → Polish)
## Risks (probability, impact, mitigation)
## Testing Strategy (unit, integration, E2E)
## Open Questions
assets/diagram-templates.md — Architecture diagram patterns (Mermaid templates)references/estimation-heuristics.md — Task sizing guidelines, common pitfalls, and estimation by task type.sdd/templates/decision-matrix.md — When to use Brief vs Full SDD planningsdd-research skill, sdd-explorer subagent/tasks command, sdd-implementer subagent