Run a manual Thai-first, read-only decision interview, confirm a compact brief, then recommend one context-fit deliverable or a gated plan-to-development handoff.
apipoj/spk
SkillsMP has collected 66 skills from apipoj/spk. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 66
- GitHub stars
- 3
- GitHub forks
- 0
Skills in this repository
Showing 40 of 66 collected skills.
Run a manual Thai-first, read-only decision interview, confirm a compact brief, then recommend one context-fit deliverable or a gated plan-to-development handoff.
สัมภาษณ์ภาษาไทยทีละ decision แบบ read-only สรุปให้ยืนยัน แล้วแนะนำงานถัดไปตาม context หรือ Plan → Dev แบบมี gate
Source text: Thai
Implement an approved software plan in small scoped slices, verify each behavior, update documentation, and report an evidence receipt.
Plan a software change from repository evidence into scoped requirements, architecture, dependency-ordered tasks, verification gates, and rollback notes.
Implement an approved software plan in small scoped slices, verify each behavior, update documentation, and report an evidence receipt.
Plan a software change from repository evidence into scoped requirements, architecture, dependency-ordered tasks, verification gates, and rollback notes.
Implement จากแผนเป็น slice เล็กที่ผ่าน test และอัปเดต docs โดยไม่ commit, push หรือเปิด PR จนกว่าจะได้รับอนุญาตแยกต่างหาก
Source text: Thai
วางแผน feature - ผลิต plan สำหรับ developer พร้อม PRD, architecture, tasks แบบ TDD, gates และ rollout notes
Source text: Thai
Apply the Buddhist Five Powers as a secular engineering balance check for confidence, effort, awareness, focus, and causal judgment.
Diagnose a reproducible software failure by tightening the red feedback loop, testing one hypothesis at a time, and proving root cause before recommending a fix.
Deploy an explicitly approved revision to a named environment, verify smoke and user-visible behavior, and preserve a tested rollback path.
Explore multiple genuinely distinct interface directions, compare them with realistic content, and record an approved design before production implementation.
Diagnose SPK installation and runtime health across supported hosts using read-only checks, then report exact failures and repair commands.
Ingest an explicitly selected source into the local project wiki with provenance, secret checks, entity links, and an append-only change record.
Guide a new SPK user from repository orientation to a reviewed plan, diagnosis, or design direction, with approval before implementation.
Prepare a focused pull request from reviewed changes, verify the exact diff and checks, and require approval before any push or remote write.
Orient agents to a repository by creating concise scoped guidance from verified source structure, commands, conventions, and code-navigation paths.
Answer a project question from the local wiki first, cite exact evidence, and use external research only when local knowledge is insufficient.
Run the repository's complete release-readiness gates, inspect version and generated-artifact consistency, and report blockers without publishing.
Review a requested diff or branch in independent correctness, security, maintainability, test, documentation, and ship-readiness passes.
Map changed files to the smallest defensible test set, run it for fast feedback, disclose unmapped paths, and require the full suite before sign-off.
Route a software-engineering request to the smallest appropriate SPK workflow, state its effect level, and preserve required approval gates.
Apply Sun Tzu as a practical engineering strategy lens for terrain, leverage, sequencing, battles to avoid, and the smallest winning move.
Take one task, ticket, or existing pull request from its source to a tested, independently reviewed pull request ready for human merge; resume exact existing work and require bound approval for Git and remote writes.
Implement behavior through strict red, green, and refactor cycles with a verified failing test first and regression evidence before completion.
Remove only verified SPK-owned project artifacts after showing exact targets, while preserving project knowledge and unrelated user files.
Audit the local project wiki for broken links, orphan pages, contradictions, stale claims, missing citations, schema drift, and secret exposure.
Apply the Buddhist Five Powers as a secular engineering balance check for confidence, effort, awareness, focus, and causal judgment.
Diagnose a reproducible software failure by tightening the red feedback loop, testing one hypothesis at a time, and proving root cause before recommending a fix.
Deploy an explicitly approved revision to a named environment, verify smoke and user-visible behavior, and preserve a tested rollback path.
Explore multiple genuinely distinct interface directions, compare them with realistic content, and record an approved design before production implementation.
Diagnose SPK installation and runtime health across supported hosts using read-only checks, then report exact failures and repair commands.
Ingest an explicitly selected source into the local project wiki with provenance, secret checks, entity links, and an append-only change record.
Guide a new SPK user from repository orientation to a reviewed plan, diagnosis, or design direction, with approval before implementation.
Prepare a focused pull request from reviewed changes, verify the exact diff and checks, and require approval before any push or remote write.
Orient agents to a repository by creating concise scoped guidance from verified source structure, commands, conventions, and code-navigation paths.
Answer a project question from the local wiki first, cite exact evidence, and use external research only when local knowledge is insufficient.
Run the repository's complete release-readiness gates, inspect version and generated-artifact consistency, and report blockers without publishing.
Review a requested diff or branch in independent correctness, security, maintainability, test, documentation, and ship-readiness passes.