@hanzlaa/rcode 2.1.0

package/rihal/templates/documentation-requirements.csv

@@ -0,0 +1,11 @@
+Document,Required,Priority,Audience,Last Updated,Status
+README.md,yes,high,all,,
+API.md,yes,high,developers,,
+CONTRIBUTING.md,yes,medium,contributors,,
+DEPLOYMENT.md,yes,high,devops,,
+ARCHITECTURE.md,yes,high,architects,,
+DEVELOPMENT.md,yes,medium,developers,,
+TESTING.md,no,medium,qa-engineers,,
+SECURITY.md,yes,high,security-team,,
+CHANGELOG.md,no,low,all,,
+TROUBLESHOOTING.md,no,medium,users,,

package/rihal/templates/github/bug-template.md

@@ -0,0 +1,53 @@
+# [Bug] {{title}}
+
+**Labels:** type:bug, priority:{{priority}}, {{area}}
+**Milestone:** {{phase}}
+**Status:** 📋 Backlog
+
+---
+
+## 🐛 Description
+
+{{description}}
+
+## 🔄 Steps to Reproduce
+
+1. {{step_1}}
+2. {{step_2}}
+3. {{step_3}}
+
+## ✅ Expected Behavior
+
+{{expected}}
+
+## ❌ Actual Behavior
+
+{{actual}}
+
+## 📧 Contact Info
+
+Reporter: {{reporter}}
+
+## 🚨 Priority
+
+- **Severity:** {{severity}} (Critical/High/Medium/Low)
+- **Impact:** {{impact}}
+
+## 🧱 Component
+
+{{component}}
+
+## 🌐 Environment
+
+- **OS:** {{os}}
+- **Browser/Runtime:** {{browser}}
+- **Version:** {{version}}
+- **Environment:** {{env}} (Production/Staging/Dev)
+
+## 📎 Additional Context
+
+{{context}}
+
+---
+
+<sub>Generated by Rihal Code — `.rihal/artifacts/bugs/{{source_file}}`</sub>

package/rihal/templates/github/epic-template.md

@@ -0,0 +1,57 @@
+# [Epic] {{title}}
+
+**Labels:** epic, priority:{{priority}}, {{area}}
+**Milestone:** {{phase}}
+**Status:** 📋 Backlog
+
+---
+
+## 🎯 Epic Vision
+
+{{vision}}
+
+## 🔍 Problem Statement
+
+{{problem}}
+
+## ✅ Success Criteria
+
+{{success_criteria}}
+
+## 👥 Target Users / Personas
+
+{{personas}}
+
+## 📦 Scope
+
+### In Scope
+{{in_scope}}
+
+### Out of Scope
+{{out_of_scope}}
+
+## ✨ Expected Features / Deliverables
+
+{{deliverables}}
+
+## 👨‍👩‍👧‍👦 Team Size Required
+
+{{team_size}}
+
+## 🔗 Dependencies & Blockers
+
+{{dependencies}}
+
+## 💭 Key Assumptions
+
+{{assumptions}}
+
+## 📊 Estimate
+
+- **Effort:** {{effort}} (XS/S/M/L/XL)
+- **Story Points:** {{story_points}}
+- **Sprints:** {{sprint_count}}
+
+---
+
+<sub>Generated by Rihal Code — `.rihal/phases/{{phase}}/tasks/{{source_file}}`</sub>

package/rihal/templates/github/feature-template.md

@@ -0,0 +1,55 @@
+# {{title}}
+
+**Labels:** type:feature, priority:{{priority}}, {{area}}
+**Milestone:** {{phase}}
+**Parent Epic:** #{{epic_number}}
+**Status:** 📋 Backlog
+
+---
+
+## 🎯 Problem Statement / Feature Description
+
+{{problem}}
+
+## 💡 Proposed Solution
+
+{{solution}}
+
+## 🔄 Alternatives Considered
+
+{{alternatives}}
+
+## 👤 Use Cases
+
+{{use_cases}}
+
+## ✅ Acceptance Criteria
+
+- [ ] {{criterion_1}}
+- [ ] {{criterion_2}}
+- [ ] {{criterion_3}}
+
+**Given/When/Then format for key flows:**
+
+> **Given** {{precondition}}
+> **When** {{action}}
+> **Then** {{expected_outcome}}
+
+## 🧱 Component
+
+{{component}}
+
+## 📊 Estimate
+
+- **Effort:** {{effort}} (XS/S/M/L/XL)
+- **Story Points:** {{story_points}}
+
+## 🔗 Related Issues
+
+- Parent epic: #{{epic_number}}
+- Blocks: {{blocks}}
+- Blocked by: {{blocked_by}}
+
+---
+
+<sub>Generated by Rihal Code — `.rihal/phases/{{phase}}/stories/{{source_file}}`</sub>

package/rihal/templates/github/task-template.md

@@ -0,0 +1,52 @@
+# {{title}}
+
+**Labels:** type:task, priority:{{priority}}, {{area}}
+**Milestone:** {{phase}}
+**Parent Feature:** #{{feature_number}}
+**Status:** 📋 Backlog
+
+---
+
+## 📝 Task Description
+
+{{description}}
+
+## ✅ Checklist
+
+- [ ] {{step_1}}
+- [ ] {{step_2}}
+- [ ] {{step_3}}
+- [ ] Tests written and passing
+- [ ] Self-review complete
+- [ ] Documentation updated if needed
+
+## 🎯 Requirements
+
+{{requirements}}
+
+## ✅ Acceptance Criteria
+
+- [ ] {{criterion_1}}
+- [ ] {{criterion_2}}
+
+## 🧱 Development Area
+
+{{area}}
+
+## 📊 Estimate
+
+- **Effort:** {{effort}} (XS/S/M/L/XL)
+- **Story Points:** {{story_points}}
+- **Hours:** ~{{hours}}
+
+## 🔗 Dependencies
+
+{{dependencies}}
+
+## 📎 Additional Context
+
+{{context}}
+
+---
+
+<sub>Generated by Rihal Code — `.rihal/phases/{{phase}}/tasks/{{source_file}}`</sub>

package/rihal/templates/milestone.md

@@ -0,0 +1,147 @@
+# Milestone Template
+
+Use this template when starting a new milestone with `/rihal:new-milestone`.
+
+## ROADMAP.md
+
+```markdown
+# Milestone: {NAME}
+
+**Started:** {ISO_DATE}
+**Status:** PLANNING
+
+## Goals
+
+Measurable outcomes for this milestone (3-5 items):
+
+- Goal 1: [Specific, measurable outcome]
+- Goal 2: [Specific, measurable outcome]
+- Goal 3: [Specific, measurable outcome]
+
+## Phases
+
+High-level breakdown of work:
+
+| # | Name | Status | Owner | Completion |
+|---|------|--------|-------|------------|
+| 1 | {Phase Name} | PLAN | {Owner} | 0% |
+
+## Success Criteria
+
+What does "done" look like?
+
+- All goals achieved
+- All phases completed
+- No critical blockers outstanding
+
+## Kill Criteria
+
+Under what conditions do we stop this milestone?
+
+- No engagement after 60 days
+- Core technical blocker cannot be resolved
+- Strategic shift makes it obsolete
+```
+
+## STATE.md
+
+```markdown
+# Milestone State: {NAME}
+
+**Last Updated:** {ISO_DATE}
+**Current Phase:** PLANNING
+
+## Decisions Made
+
+Log of all significant decisions with context:
+
+| Decision | Rationale | Date | Owner |
+|----------|-----------|------|-------|
+| {Decision} | {Why} | {Date} | {Person} |
+
+## Blockers
+
+Active blockers preventing progress:
+
+- [Blocker 1] (since date, assigned to person, depends on X)
+- [Blocker 2] (since date, assigned to person, depends on Y)
+
+## Active Workstreams
+
+Parallel work streams running concurrently:
+
+- Workstream 1: {Description} (owner, expected completion)
+- Workstream 2: {Description} (owner, expected completion)
+
+## Quick Tasks Completed
+
+Small items completed outside the main phase structure:
+
+| Task | Date | Owner |
+|------|------|-------|
+| {Task} | {Date} | {Person} |
+
+## Metrics
+
+Current health metrics:
+
+- Phase completion: X%
+- Velocity: {points/day}
+- Risk level: {HIGH|MEDIUM|LOW}
+```
+
+## REQUIREMENTS.md
+
+```markdown
+# Requirements: {NAME}
+
+**Updated:** {ISO_DATE}
+
+## User Stories
+
+Features requested from user perspective:
+
+```gherkin
+As a {user}, I want {capability} so that {benefit}
+Acceptance Criteria:
+  - [ ] Criterion 1
+  - [ ] Criterion 2
+```
+
+## Technical Specifications
+
+Implementation-level details:
+
+- {Spec 1}
+- {Spec 2}
+
+## Acceptance Criteria
+
+How do we validate completion?
+
+- [ ] Criteria 1 met and tested
+- [ ] Criteria 2 met and tested
+
+## Out of Scope
+
+What are we explicitly NOT doing?
+
+- Out of scope item 1
+- Out of scope item 2
+
+## Dependencies
+
+What must be done before this milestone can succeed?
+
+- External dependency 1
+- Internal dependency 1
+```
+
+## Best Practices
+
+1. **Keep goals measurable** — "Increase signup rate by 15%" not "improve signup"
+2. **Name owners for every phase** — accountability matters
+3. **Update STATE.md weekly** — don't let decisions get lost
+4. **Kill criteria first** — know what stops work before starting
+5. **Scope creep signal** — if new phases appear, escalate
+6. **Document assumptions** — every phase starts with assumptions listed

package/rihal/templates/projects/api-backend/PROJECT.md

@@ -0,0 +1,37 @@
+# {{project_name}} — API Backend
+
+**Template:** api-backend
+**Created:** {{date}}
+
+## What we're building
+A headless API for {{use_case}}. Consumers are other services, internal apps, or third-party integrations — not end users directly.
+
+## API surface
+- **Protocol:** REST / GraphQL / gRPC — pick one, justify in an ADR
+- **Versioning strategy:** {{versioning}} (URL-prefix vs header vs dated)
+- **Auth:** API keys + scoped tokens
+
+## Primary consumers
+- {{consumer_1}}
+- {{consumer_2}}
+
+## Performance targets
+- p50 latency: {{p50}} · p95: {{p95}} · p99: {{p99}}
+- Throughput: {{rps}} req/s sustained
+- Availability: {{slo}}
+
+## Non-negotiables
+- Every endpoint is idempotent or explicitly documented as non-idempotent
+- Breaking changes ship under a new version — never mutate existing endpoints
+- Errors follow a consistent schema (code, message, request_id)
+
+## Explicitly out of scope
+- Frontend / dashboards (separate project)
+- Self-serve signup UI
+
+## Key risks
+- Scope drift into full-product features → resist
+- Early API shape locks in; expensive to change once consumers integrate
+
+## Evolution
+_(Updated after each phase completion by `/rihal:execute`.)_

package/rihal/templates/projects/api-backend/REQUIREMENTS.md

@@ -0,0 +1,38 @@
+# {{project_name}} — Requirements
+
+Canonical REQ IDs for an API backend. Edit titles/acceptance, do not rename IDs once phases reference them.
+
+---
+
+## REQ-SCAFFOLD — Project scaffolding
+Framework, DB, migrations, local dev loop, CI, linting — all wired and tested.
+
+## REQ-CI — Continuous integration
+Every PR runs lint + type-check + tests. Main branch protected.
+
+## REQ-AUTH-API — API key authentication
+Keys are prefixed-and-hashed in storage. Issuance, rotation, revocation all work. Revocation takes effect within one request.
+
+## REQ-SCOPES — Scoped tokens
+Keys declare scopes. Endpoints enforce required scope. Denial is auditable.
+
+## REQ-RESOURCES — Core resources
+The primary resources this API exists for are implemented end-to-end with CRUD (or equivalent) and tested.
+
+## REQ-CONTRACT — API contract as source of truth
+OpenAPI / GraphQL schema / .proto checked in. Contract tests fail when implementation drifts.
+
+## REQ-RATE-LIMIT — Rate limiting
+Per-key rate limits prevent runaway clients. 429 responses include retry-after and current-limit headers.
+
+## REQ-QUOTAS — Tier-based quotas
+Daily/monthly quotas enforceable per tier. Quota state visible to clients via a headers-or-endpoint mechanism.
+
+## REQ-SDK — First-party SDK
+At least one SDK exists, is published, and has a working quickstart example.
+
+## REQ-DOCS — Public docs
+Docs generated from the API contract + hand-written guides for the top use cases. Includes authentication, errors, rate limits, changelog.
+
+## REQ-OBSERVABILITY-API — SLOs + monitoring
+p50/p95/p99 + error rate tracked per endpoint and per consumer. Status page is public. Top-5 failure runbooks exist.

package/rihal/templates/projects/api-backend/ROADMAP.md

@@ -0,0 +1,92 @@
+# {{project_name}} — Roadmap
+
+**Milestone: M1 — v1 API GA** (v1.0)
+Template: api-backend · Seeded {{date}}
+
+---
+
+## Phase 01 — Scaffolding
+
+**Goal:** Framework chosen, DB wired, migrations working, CI green. No business endpoints yet.
+
+**Delivers:**
+- Project skeleton in chosen framework
+- Database + migration tool
+- Local dev + CI both run the full test suite in <2 minutes
+- Linting + formatting enforced
+
+**Requirements:** REQ-SCAFFOLD, REQ-CI
+
+---
+
+## Phase 02 — Auth + API keys
+
+**Goal:** Every endpoint requires a valid key. Keys have scopes. Key rotation + revocation works.
+
+**Delivers:**
+- API key issuance flow (token prefix + hashed secret storage)
+- Scope model (read vs write, per-resource)
+- Revocation endpoint that takes effect within one request cycle
+- Rate limit on auth failures to prevent key enumeration
+
+**Requirements:** REQ-AUTH-API, REQ-SCOPES
+
+---
+
+## Phase 03 — Core resources + contract
+
+**Goal:** The primary resources this API exists to serve are implemented end-to-end with tests.
+
+**Delivers:**
+- CRUD (or equivalent) for the 3-5 primary resources
+- OpenAPI (or GraphQL schema / .proto) checked into the repo as the source of truth
+- Contract tests that fail if implementation drifts from the schema
+- Consistent error schema across all endpoints
+
+**Requirements:** REQ-RESOURCES, REQ-CONTRACT
+
+**Depends on:** Phase 02
+
+---
+
+## Phase 04 — Rate limiting + quotas
+
+**Goal:** A single misbehaving client cannot take down the service. Quotas are visible to clients.
+
+**Delivers:**
+- Per-key rate limit (token bucket or sliding window)
+- Per-tier daily/monthly quota
+- `429` responses include retry-after + current limit headers
+- Dashboard for internal staff to see top talkers
+
+**Requirements:** REQ-RATE-LIMIT, REQ-QUOTAS
+
+---
+
+## Phase 05 — SDK + public docs
+
+**Goal:** A competent developer can integrate in under 30 minutes without help.
+
+**Delivers:**
+- At least one first-party SDK (language chosen to match top consumer)
+- Docs site generated from OpenAPI/schema + hand-written guides
+- Runnable examples (not just snippets — actual curl/SDK calls that work)
+- Changelog
+
+**Requirements:** REQ-SDK, REQ-DOCS
+
+**Depends on:** Phase 03
+
+---
+
+## Phase 06 — Observability + SLOs
+
+**Goal:** Published SLOs, measured SLIs, alerting that fires before customers notice.
+
+**Delivers:**
+- p50/p95/p99 latency tracked per endpoint
+- Error rate per endpoint + per consumer
+- Public status page
+- Runbooks for the top 5 failure modes
+
+**Requirements:** REQ-OBSERVABILITY-API

package/rihal/templates/projects/api-backend/template.yaml

@@ -0,0 +1,17 @@
+name: api-backend
+display: "API Backend"
+description: "Headless API service — authentication, data model, public API, SDK, docs"
+recommended_modules:
+  - core
+  - execution
+phases:
+  - "01 — Scaffolding (framework, DB, migrations, CI)"
+  - "02 — Auth + API keys"
+  - "03 — Core resources + REST/GraphQL contract"
+  - "04 — Rate limiting + quotas"
+  - "05 — SDK + public docs"
+  - "06 — Observability + SLOs"
+next_steps: |
+  Seeded. Common follow-ups:
+    /rihal:council REST vs GraphQL vs both for this API?
+    /rihal:plan phase 01

package/rihal/templates/projects/mobile-app/PROJECT.md

@@ -0,0 +1,37 @@
+# {{project_name}} — Mobile App
+
+**Template:** mobile-app
+**Created:** {{date}}
+
+## What we're building
+A mobile app for {{target_user}} that solves {{core_problem}}. iOS + Android from day one.
+
+## Target user
+- **Who:** {{user_segment}}
+- **Context of use:** {{context}} (commute, at-desk, on-site, one-handed, etc.)
+- **Device assumptions:** {{device_assumptions}} (min OS, connectivity, battery tolerance)
+
+## Core value loop
+_(Describe the repeatable loop — 2-4 steps — that drives retention.)_
+
+1. {{step_1}}
+2. {{step_2}}
+3. {{step_3}}
+
+## Non-negotiables
+- Works offline for the core action (mobile users drop connectivity often)
+- Respects device permissions — no surprise background GPS, no over-asking
+- Respect platform conventions (iOS HIG, Material 3) before bespoke UX
+
+## Explicitly out of scope
+- Web app in v1
+- Tablet-optimized UI (phone-first)
+- Apple Watch / Wear OS
+
+## Key risks
+- **App Store review:** a single rejection can delay launch by 1-2 weeks; plan for it
+- **Performance on low-end Android:** test on a real <$200 device early
+- **Push opt-in rate:** <30% is common; design core loop to work without push
+
+## Evolution
+_(Updated after each phase completion by `/rihal:execute`.)_

package/rihal/templates/projects/mobile-app/REQUIREMENTS.md

@@ -0,0 +1,32 @@
+# {{project_name}} — Requirements
+
+Canonical REQ IDs for a mobile app. Edit titles/acceptance, do not rename IDs once phases reference them.
+
+---
+
+## REQ-MOBILE-SCAFFOLD — App scaffolding
+Both platforms build, run, and navigate between placeholder core screens.
+
+## REQ-MOBILE-CI — Continuous delivery to testers
+Every main merge produces a signed build available to internal testers on both platforms within ~30 min.
+
+## REQ-MOBILE-AUTH — Authentication
+Sign up + sign in flows work on both platforms. Session persists. At least one social provider.
+
+## REQ-ONBOARDING — Activation flow
+New user can reach the core screen in under 60 seconds on a mid-tier device. Drop-off tracked per onboarding step.
+
+## REQ-MOBILE-CORE — Core feature
+The one thing this app is for works end-to-end on both platforms, with analytics on the 3-5 events that prove it.
+
+## REQ-MOBILE-OFFLINE — Offline + sync
+Core action writes locally, syncs when online. Conflicts have a defined resolution. UI states for pending/syncing/failed.
+
+## REQ-MOBILE-PUSH — Push notifications
+APNs + FCM wired. Permission priming before the OS dialog. Opt-out respected. In-app inbox for missed notifications.
+
+## REQ-DEEPLINKS — Universal / app links
+Deep links open the app if installed, route to the correct screen, and fall back to web / store if not.
+
+## REQ-MOBILE-LAUNCH — Store launch
+Listings live on both stores with screenshots, privacy labels, demo account for Apple review, privacy policy URL.