Plan Module
A Claude skill from Karthick-Ramachandran/persist-os.
Install
$ agentstack add skill-karthick-ramachandran-persist-os-plan-module ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-karthick-ramachandran-persist-os-plan-module) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill: Plan Module
Purpose
Turn a module request into a complete delivery workflow before implementation starts.
Inputs
- Module name or request.
- Product goal or user need.
- Existing architecture, feature, or module docs.
- Known constraints or priority stage.
Required Reading
AGENTS.mddocs/00-product/PRD.mddocs/10-architecture/ARCHITECTURE.mddocs/20-security/SECURITY_MODEL.mddocs/50-quality/TESTING_STRATEGY.mddocs/60-engineering/ENGINEERING_STANDARDS.mddocs/ai/MODULE_DELIVERY_WORKFLOW.md- Relevant ADRs under
docs/adrs/
Output Files
docs/40-features/F-###--module/delivery docs (PRD, ACCEPTANCE, ARCHITECTURE_IMPACT,
PLAN, TASKS, TESTPLAN, REVIEW, COMPLETIONREPORT).
docs/30-modules//MODULE.mddocs/30-modules//TASKS.mddocs/30-modules//TEST_PLAN.mddocs/30-modules//DECISIONS.md
Process
- Create a module brief: ownership, non-ownership, public interfaces, users, and use cases.
- Define behavior and edge cases.
- Write testable acceptance criteria.
- Document architecture impact, dependency impact, config impact, template impact, and ADR needs.
- Write the test plan from acceptance criteria, security invariants, and regression risk.
- Break work into ordered tasks with status, scope, acceptance, tests, and do-not-do boundaries.
- Mark implementation as blocked until the first task is selected.
Stop Conditions
Stop and request human decision if:
- The module ownership or public interface is unclear.
- The module conflicts with accepted ADRs or architecture docs.
- The module conflicts with engineering standards.
- The module requires runtime network, telemetry, cloud, MCP, AI API, auth, secrets, storage, or
file write behavior changes without ADR or security review.
- The user asks to implement before PRD, acceptance, architecture impact, test plan, and tasks
exist.
Quality Bar
- The module is planned as a mini product, not a file list.
- PRD, acceptance, architecture impact, test plan, and tasks are all present.
- Tasks are small enough to execute one at a time.
- Module memory captures what future agents need to remember.
- No implementation code is written by this skill.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Karthick-Ramachandran
- Source: Karthick-Ramachandran/persist-os
- License: MIT
- Homepage: https://persist-os.pages.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.