القائمة
Generate technical implementation plan from feature specification. Use after creating spec. Triggers on: create plan, technical plan, implementation design.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | plan |
| description | Generate technical implementation plan from feature specification. Use after creating spec. Triggers on: create plan, technical plan, implementation design. |
Create detailed technical plans that translate feature specifications into implementation designs.
This skill is Step 2 of 6 in the Relentless workflow:
specify → plan → tasks → analyze → implement
What flows from spec:
What flows to tasks:
The technical plan MUST include concrete test specifications:
The agent MUST write tests BEFORE implementation code.
This is non-negotiable. Plans without test specifications are incomplete.
spec.md)plan.md in the feature directoryFind the current feature directory:
relentless/features/ for the most recent featurespec.md existsspec.md and extract routing preferenceauto: good | allow free: yesExample:
Spec says: **Routing Preference**: auto: genius | allow free: no
Plan carries: **Routing Preference**: auto: genius | allow free: no
Read these files:
Note all MUST and SHOULD rules from constitution - these are quality gates.
Using the template at templates/plan.md, create a plan with:
1. Technical Overview
2. Data Models
3. API Contracts
4. Implementation Strategy
5. Test Specifications (MANDATORY)
6. Security Considerations
7. Rollout Plan
Validate the plan against constitution:
Before completing the plan, validate:
any types planned in TypeScriptMUST rules: Required, plan must follow these SHOULD rules: Best practices, document any deviations
If plan violates MUST rules, revise until compliant.
If plan generates any doubts, interview the user about them with insightful questions to improve the plan.
relentless/features/NNN-feature/plan.md.claude/skills/validators/scripts/validate-plan.sh "relentless/features/NNN-feature/plan.md"
/relentless.tasks# Technical Implementation Plan: User Authentication
**Routing Preference**: auto: good | allow free: yes
## Technical Overview
**Architecture:** Three-tier (API, Service, Data)
**Stack:** Node.js, TypeScript, PostgreSQL
**Authentication:** JWT tokens with refresh mechanism
## Data Models
### User Table
\`\`\`sql
CREATE TABLE users (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
email VARCHAR(255) UNIQUE NOT NULL,
password_hash VARCHAR(255) NOT NULL,
confirmed BOOLEAN DEFAULT FALSE,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP DEFAULT NOW()
);
CREATE INDEX idx_users_email ON users(email);
\`\`\`
## API Contracts
### POST /api/auth/register
**Request:**
\`\`\`json
{
"email": "user@example.com",
"password": "password123"
}
\`\`\`
**Response (201):**
\`\`\`json
{
"id": "uuid",
"email": "user@example.com",
"message": "Confirmation email sent"
}
\`\`\`
## Test Specifications (MANDATORY)
### Test File Structure
\`\`\`
tests/
├── unit/
│ ├── auth/
│ │ ├── password.test.ts
│ │ └── email-validation.test.ts
│ └── token/
│ └── jwt.test.ts
├── integration/
│ └── auth/
│ ├── register.test.ts
│ └── login.test.ts
└── e2e/
└── auth-flow.test.ts
\`\`\`
### Unit Tests
| Component | Test File | Functions to Test |
|-----------|-----------|-------------------|
| Password | `tests/unit/auth/password.test.ts` | hashPassword, verifyPassword |
| Email | `tests/unit/auth/email-validation.test.ts` | validateEmail |
| JWT | `tests/unit/token/jwt.test.ts` | generateToken, verifyToken |
### Integration Tests
| Flow | Test File | Scenarios |
|------|-----------|-----------|
| Register | `tests/integration/auth/register.test.ts` | success, duplicate email, invalid input |
| Login | `tests/integration/auth/login.test.ts` | success, wrong password, unconfirmed |
### Mock Requirements
- Database mock (in-memory or test container)
- Email service mock (no actual sends)
- Time mock for token expiration tests
### Coverage Targets
- Unit: 90% minimum (critical auth code)
- Integration: All happy paths + error paths
- E2E: Complete registration and login flow
## Constitution Compliance
**MUST Rules Checked:**
- [x] TDD is mandatory - test specs defined above
- [x] Quality gates defined - typecheck, lint, test commands
- [x] Routing preference carried from spec
- [x] No `any` types planned
- [x] Error handling strategy defined
**If any MUST rule cannot be satisfied, document the exception and remediation plan.**
Generate quality validation checklist from spec, plan, and tasks. Use after creating tasks. Triggers on: create checklist, quality checklist, validation checklist.
Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.
Distill learnings from completed features and propose amendments to constitution.md or prompt.md. Use after feature completion. Triggers on: capture learnings, learn from feature, distill learnings, relentless learn.
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Generate dependency-ordered user stories and tasks from plan. Use after creating plan. Triggers on: create tasks, generate user stories, break down implementation.
Convert tasks.md to prd.json with smart routing classification. Use after creating tasks. Triggers on: convert to prd, generate prd.json, convert tasks.