Plan Feature
A Claude skill from Karthick-Ramachandran/persist-os.
Install
$ agentstack add skill-karthick-ramachandran-persist-os-plan-feature ✓ 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-feature) 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 Feature
Purpose
Turn product intent into a scoped engineering plan that an implementation agent can follow safely.
Inputs
- Feature PRD.
- Acceptance criteria.
- Relevant module or architecture docs.
- Known constraints or release target.
Required Reading
docs/10-architecture/ARCHITECTURE.mddocs/10-architecture/FILE_WRITE_POLICY.mddocs/20-security/SECURITY_MODEL.mddocs/50-quality/QUALITY_GATES.mddocs/60-engineering/ENGINEERING_STANDARDS.md- Relevant feature docs under
docs/40-features/ - Relevant module docs under
docs/30-modules/ - Relevant ADRs under
docs/adrs/
Output Files
docs/40-features//PLAN.mddocs/40-features//TASKS.mddocs/40-features//ARCHITECTURE_IMPACT.mddocs/40-features//TEST_PLAN.md
Process
- Restate the feature objective and acceptance criteria.
- Identify modules, docs, templates, and tests affected.
- Document architecture impact and ADR needs.
- Break work into ordered tasks with clear completion evidence.
- Define tests from requirements, risk, security invariants, and regressions.
- For module requests, treat the module as a mini product and create feature delivery docs before
implementation tasks.
Stop Conditions
Stop and request human decision if:
- Requirements are missing or contradictory.
- Architecture impact cannot be determined.
- The plan conflicts with engineering standards.
- A task requires changing accepted non-goals.
- A module request tries to start implementation before PRD, acceptance, architecture impact, test
plan, and tasks exist.
Quality Bar
- Tasks are ordered and independently reviewable.
- Tests map to acceptance criteria and risks.
- Architecture impact is explicit.
- Engineering standards are accounted for in tasks and completion evidence.
- The plan does not include implementation code when only planning is requested.
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.