Skip to content
Back to skills

1902 Kiro Ca762c38

ASecurity

How to use planning-with-files with [Kiro](https://kiro.dev). ---

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
toolsgoshellbashgit

Works with

  • cli

Security analysis

A93/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 1902-kiro_ca762c38 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 1902 Kiro Ca762c38?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 1902 Kiro Ca762c38
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-1902-kiro-ca762c38/badge)](https://www.skillsdirectory.com/skills/tools-only-1902-kiro-ca762c38)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Kiro Setup

How to use planning-with-files with [Kiro](https://kiro.dev).

---

## Important: Kiro Uses Steering Files

Kiro doesn't use the standard `SKILL.md` format. Instead, it uses **Steering Files** — markdown documents in `.kiro/steering/` that provide persistent project knowledge.

See: [Kiro Steering Docs](https://kiro.dev/docs/cli/steering/)

---

## What This Integration Adds

```
.kiro/
├── steering/
│   ├── planning-workflow.md   # Core workflow and quick start
│   ├── planning-rules.md      # Critical rules and error protocols
│   └── planning-templates.md  # Templates for task_plan, findings, progress
└── scripts/
    ├── init-session.sh        # Initialize planning files (Bash)
    ├── init-session.ps1       # Initialize planning files (PowerShell)
    ├── check-complete.sh      # Verify phases complete (Bash)
    └── check-complete.ps1     # Verify phases complete (PowerShell)
```

---

## Installation (Workspace)

Copy to your project:

```bash
git clone https://github.com/OthmanAdi/planning-with-files.git
cp -r planning-with-files/.kiro .kiro
rm -rf planning-with-files
```

---

## Installation (Global)

Copy to your global Kiro config:

```bash
git clone https://github.com/OthmanAdi/planning-with-files.git
mkdir -p ~/.kiro/steering ~/.kiro/scripts
cp planning-with-files/.kiro/steering/* ~/.kiro/steering/
cp planning-with-files/.kiro/scripts/* ~/.kiro/scripts/
rm -rf planning-with-files
```

Global steering applies to all your projects.

---

## Usage

1. Start Kiro in your project
2. For complex tasks, create the planning files:

```bash
# Using the init script
bash .kiro/scripts/init-session.sh

# Or manually create:
# - task_plan.md
# - findings.md
# - progress.md
```

3. The steering files automatically guide Kiro to:
   - Create plans before complex tasks
   - Update findings after research
   - Log progress and errors
   - Follow the 3-strike error protocol

---

## How Steering Works

Kiro loads steering files automatically in every interaction. The planning guidance becomes part of Kiro's project understanding without you needing to explain it each time.

| File | Purpose |
|------|---------|
| `planning-workflow.md` | Core pattern and quick start |
| `planning-rules.md` | Critical rules and error handling |
| `planning-templates.md` | Copy-paste templates |

---

## Helper Scripts

```bash
# Initialize all planning files
bash .kiro/scripts/init-session.sh

# Windows PowerShell
powershell -ExecutionPolicy Bypass -File .kiro/scripts/init-session.ps1

# Verify all phases complete
bash .kiro/scripts/check-complete.sh
```

---

## Notes

- Steering files are loaded automatically — no manual invocation needed
- Workspace steering (`.kiro/`) takes priority over global (`~/.kiro/`)
- Planning files (`task_plan.md`, etc.) go in your project root, not in `.kiro/`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.